Launchpad has imported 4 comments from the remote bug at https://bugzilla.gnome.org/show_bug.cgi?id=679294.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2012-07-03T01:10:00+00:00 Damián Nohales wrote: Most GUIs, like MacOS X, Microsoft Windows and Qt handle the keyboard bindings for its treeviews in the same way: user can easily expand, collapse and move into tree nodes using only the arrow keys. In Gtk+, however, is quite different. User needs to press "plus" and "minus" key to collapse and expand nodes, leaving Right and Left arrows with essentially null functionality. Well yeah, that keys allow to move horizontally into row cells. Seeing many of the applications written using Gtk+, there are not many cases where user find useful moving horizontally across the row with the keyboard, most GtkTreeView that I see are simple and used only to show information. So I guess the current GtkTreeView behaviour is crazy, not useful in most cases, goes against intuition and against good User Experience. I'm really not familiar with Gtk+ programming but, as user, I find this "bug" extremely annoying in my day to day. So, I make some changes in Gtk+ to enhance (from my point of view) the behavior of GtkTreeView with the keyboard. The attached patch to the 3.4 branch modifies the default GtkTreeView behaviour with the keyboard, expanding nodes with the right arrow and collapsing it with left arrow, selecting parent and child nodes when appropriate: - When user press Left on a collapsed node, Gtk+ select the parent node. - When user press right on an expanded node, Gtk+ select the first child node. Users that want to navigate into cells horizontally (as I can see, a non frecuent use case) will need to press Ctrl+<Left|Right>. Users can still move to the parent node with the Backspace key, without collapsing anything. I don't know exactly if this behavior change break some expected behavior to application programmer, I hope not. A last question, Why do you implemented the current GtkTreeView behavior knowing the big difference with other tested GUIs? Best Regards! Reply at: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1020756/comments/0 ------------------------------------------------------------------------ On 2012-07-03T01:11:18+00:00 Damián Nohales wrote: Created attachment 217896 treeview: change keyboard bindings behaviour Reply at: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1020756/comments/1 ------------------------------------------------------------------------ On 2012-07-15T13:14:24+00:00 Kris-z wrote: (In reply to comment #0) > Users that want to navigate into cells horizontally (as I can see, a non > frecuent use case) will need to press Ctrl+<Left|Right>. Users can still move > to the parent node with the Backspace key, without collapsing anything. Just to give a little background, this was tried in 2006, see: https://bugzilla.gnome.org/show_bug.cgi?id=105895#c27 And reverted a year later due to complaints: https://bugzilla.gnome.org/show_bug.cgi?id=105895#c29 >From there on I pretty much gave up. As I mentioned in comment 29 in 105985; >a sophisticated plan is likely needed where you "detect" the kind of tree view >(list or tree, many editable cells or not, long horizontally stretching rows, >etc.) and base the keyboard bindings based on that. Reply at: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1020756/comments/5 ------------------------------------------------------------------------ On 2018-02-10T04:36:12+00:00 Matthias Clasen wrote: We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue for it. Reply at: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1020756/comments/12 ** Changed in: gtk Status: Unknown => Expired ** Changed in: gtk Importance: Unknown => High ** Bug watch added: bugzilla.gnome.org/ #105895 https://bugzilla.gnome.org/show_bug.cgi?id=105895 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1020756 Title: GtkTreeView keyboard binding are not intituive Status in GTK+: Expired Status in gnucash package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Triaged Bug description: Most GUIs, like MacOS X, Microsoft Windows and Qt handle the keyboard bindings for its treeviews in the same way: user can easily expand, collapse and move into tree nodes using only the arrow keys. In Gtk+, however, is quite different. User needs to press "plus" and "minus" key to collapse and expand nodes, leaving Right and Left arrows with essentially null functionality. Well yeah, that keys allow to move horizontally into row cells. Seeing many of the applications written using Gtk+, there are not many cases where user find useful moving horizontally across the row with the keyboard, most GtkTreeView that I see are simple and used only to show information. So I guess the current GtkTreeView behaviour is crazy, not useful in most cases, goes against intuition and against good User Experience. I'm really not familiar with Gtk+ programming but, as user, I find this "bug" extremely annoying in my day to day. So, I make some changes in Gtk+ to enhance (from my point of view) the behavior of GtkTreeView with the keyboard. The attached patch to the 3.4 branch modifies the default GtkTreeView behaviour with the keyboard, expanding nodes with the right arrow and collapsing it with left arrow, selecting parent and child nodes when appropriate: - When user press Left on a collapsed node, Gtk+ select the parent node. - When user press right on an expanded node, Gtk+ select the first child node. Users that want to navigate into cells horizontally (as I can see, a non frecuent use case) will need to press Ctrl+<Left|Right>. Users can still move to the parent node with the Backspace key, without collapsing anything. I don't know exactly if this behavior change break some expected behavior to application programmer, I hope not. A last question, Why Gtk+ programmers implemented the current GtkTreeView behavior knowing the big difference with other tested GUIs? Best Regards! To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1020756/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
