Update of bug #25659 (project gnustep):
Status: Confirmed => Ready For Test
Assigned to: None => FredKiefer
Open/Closed: Open => In Test
_______________________________________________________
Follow-up Comment #2:
What you have to do to get this correctly working is to set the gloabl
default GSModifiersAreKeys to YES. The documentation of back explains it like
this:
On some keyboards, the default X11 mapping includes keycodes that are mapped
to one or another modifier keysym depending on whether 'shift' (or in some
cases, another key) is pressed. This is the case on some Apple USB keyboards
for example: one key to the left of the spacebar maps to "Option" without
shift pressed, and "Alt" with shift pressed. Such keyboard mappings are often
useful in non-English contexts to access accents or non-Roman characters.
However if such a key is used as a modifier in GNUstep problems can occur
when trying to use the modifier in conjunction with a shifted character. In
particular, you will need to hit and release the modifier and the shift key in
a particular order, or else things will not work as expected, and the modifier
may become "stuck". If you experience such a problem, set
<code>GSModifiersAreKeys</code> to <code>YES</code>.
What surprises me is that I didn't have to set this before, but with my new X
server I seem to need it. Perhaps we should switch the default of this setting
to YES? Could other people out there please test, which setting works best for
them?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?25659>
_______________________________________________
Nachricht geschickt von/durch Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep
