Bug 9653 - gnome tree can't be opened with '+' and de-keyboard layout
Summary: gnome tree can't be opened with '+' and de-keyboard layout
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gtk+
Version: 6.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Owen Taylor
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-02-21 18:27 UTC by Harald Hoyer
Modified: 2008-05-01 15:37 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2001-07-11 13:06:00 UTC


Attachments (Terms of Use)

Description Harald Hoyer 2000-02-21 18:27:42 UTC
gnome tree widget can be opened by '+' and
 Section "Keyboard"
     Protocol    "Standard"
     LeftAlt         Meta
     RightAlt        Meta
     ScrollLock      Compose
     RightCtl        Control
     XkbRules    "xfree86"
     XkbModel    "pc102"
     XkbLayout   "de"
     XkbVariant  "nodeadkeys"
 EndSection

 it can only be closed by '-'
 tested with gnomecc ... :(

Comment 1 Preston Brown 2000-02-24 02:25:59 UTC
havoc:  can you make heads or tails of what this means?

Comment 2 Havoc Pennington 2000-02-24 22:33:59 UTC
Can you explain in more detail? Is the problem that the "+" key doesn't expand
tree nodes? Are you using "+" on the numeric keypad, or regular "+"?

Comment 3 Harald Hoyer 2000-02-25 07:43:59 UTC
I did use the regular +, the numeric didn't come in my mind. :)

Comment 4 Havoc Pennington 2000-02-25 17:01:59 UTC
So for me "+" expands, "-" collapses, and "=" toggles the state. "+" just does
nothing for you? What keysym does your "+" send?

Comment 5 Harald Hoyer 2000-02-28 13:56:59 UTC
KeyPress event, serial 30, synthetic NO, window 0x3800001,
    root 0x26, subw 0x0, time 2558882897, (91,86), root:(1188,871),
    state 0x0, keycode 35 (keysym 0x2b, plus), same_screen YES,
    XLookupString gives 1 characters:  "+"

KeyRelease event, serial 30, synthetic NO, window 0x3800001,
    root 0x26, subw 0x0, time 2558882964, (91,86), root:(1188,871),
    state 0x0, keycode 35 (keysym 0x2b, plus), same_screen YES,
    XLookupString gives 1 characters:  "+"
--------
Numeric "+" works with no problems

Comment 6 Havoc Pennington 2000-02-29 19:58:59 UTC
OK, I know why this problem happens: basically the keybinding is "Shift and the
plus key," rather than simply "the plus keysym." It's a GTK bug, so I'll move it
to GTK.

Comment 7 Harald Hoyer 2000-11-03 14:11:39 UTC
Does this ever get fixed???

Comment 8 Owen Taylor 2001-07-10 22:06:54 UTC
It's quite hard to fix since it takes sensitivity
to the keyboard layout to know what to do. We will have
this fixed for GTK+-2.0.

Comment 9 Harald Hoyer 2001-07-11 08:35:51 UTC
XLookupString gives 1 characters:  "+"
doesn't that work with all layouts?


Comment 10 Owen Taylor 2001-07-11 13:05:57 UTC
The question is, is <Shift> an ignorable modifier for a given accelerator?

For '+' it is, for 'F1' it is not. Knowing which is the case for a 
particular accelerator key, takes sensitivity to the keyboard layout.

Of course, in this case, there is a simple workaround:

Fri Feb 16 20:09:42 2001 Owen Taylor <otaylor@redhat.com>

* gtk/gtkctree.c (gtk_ctree_class_init): Add bindings
for unshifted + and shifted = for non-us keyboards.
Make <Control>+ and <Control>- work as well as
<Control>KP_Plus, <Control>KP_Minus for recursive
open/close. (#2682, Reni Seindal)

Which was in 1.2.9 / 7.1. :-)


Note You need to log in before you can comment on or make changes to this bug.