Gestures treeview does not look like a treeview #6317

Closed
feerrenrut opened this Issue Aug 30, 2016 · 1 comment

Comments

Projects
None yet
2 participants
@feerrenrut
Contributor

feerrenrut commented Aug 30, 2016

While looking at parts of the GUI I noticed that the gestures tree view does not really have any visual indication that it is a tree view. Instead it just looks like a list of text items. This seems to be the result of not having a single root to the tree, and is reproducible in the wxPython samples.

To make this more obvious we could add a single root, eg "Gestures" and expand the children (components) of this by default.

@feerrenrut

This comment has been minimized.

Show comment
Hide comment
@feerrenrut

feerrenrut Aug 30, 2016

Contributor

@jcsteh what would you think about this?

Contributor

feerrenrut commented Aug 30, 2016

@jcsteh what would you think about this?

feerrenrut added a commit that referenced this issue Sep 29, 2016

incubates #6287
For issues:
 #6317 (Gestures treeview does not look like a treeview)
 #5548 (Text control to specify the path when creating a portable copy is
quite narrow)
 #6342 (Spacing between labels and combo boxes)
 #6343 (Inconsistency with vertical spacing between checkbox/label
options)
 #6349 (input gestures dialog tree view too small)

Merge branch 'fixGuiAlignmentIssues' into next

Conflicts:
	source/gui/settingsDialogs.py
          - voice settings (speak numbers as)
          - SpeechSymbolsDialog (mouse interaction)

@nvaccessAuto nvaccessAuto added this to the 2016.4 milestone Oct 13, 2016

feerrenrut added a commit that referenced this issue Oct 13, 2016

Update changes file for PR #6287, #6402, #6339
For PR #6287 - Various padding and alignment issues have been resolved. (#6317, #5548, #6342, #6343, #6349)
For PR #6402 - The document formatting dialog has been adjusted so that the contents scrolls. (#6348)
For PR #6339 - Adjusted the layout of the symbols pronunciation dialog so the full width of the dialog is used for the symbols list. (#6101)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment