in the 20030115 build, if you bind an action to, for
example Meta-C, when pressing Meta-C the action will be
executed and a C will be printed. I do not have this
problem on my Linux box.
This could also be related to Support Request 685800
("Keyboard problem"). Apparently, on Spanish keyboards,
ALT-Gr+{ and ALT-Gr+[ don't work, but ALT-Gr+} and ALT-Gr+]
do work.
Perhaps we could figure out how to write some unit tests
simulating different keyboard layouts to demonstrate these
bugs on other platforms.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I wrote a test that catches this problem. It is in a new
file, edu.rice.cs.drjava.ui.DefinitionsPaneTest However, I
still have no idea how to fix the problem. Perhaps the meta
key is not being registered somewhere as a modifier key. I
have not been able to findthe place where it should be if
this is the case.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Take a look at KeyStrokeOption in the config package, and its accompanying test. There's already some things we have to deal with for ctrl/command and alt/option on the Mac. Meta might just have a different name we need to parse.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Pressing a key combination like meta-a triggers a whole
series of KeyEvents. First is a KEY_PRESSED with keyCode of
KeyEvent.VK_META. Next is a KEY_PRESSED with keyCode of
KeyEvent.VK_A. If meta-a is bound to anything, this
KeyEvent will trigger the action. This event is not passed
by DefinitionsPane to super.processKeyEvent(...). Next comes
a KEY_TYPED with keyCode of KeyEvent.VK_UNKNOWN and keyChar
of "a". This is the event that triggered the extraneous
input in super.processKeyEvent(...), so I rewrote
DefinitionsPane.processKeyEvent(...) to throw away these
KeyEvent's. After the KEY_TYPED, there are KEY_RELEASED
events for "a" and meta symmetrical to the KEY_PRESSED
events, if anyone cares. You can see an example in
DefinitionsPaneTest.testMetaKeyPress().
So bottom line, I am closing this bug, because the original
bug is fixed. The alt-graph+{ support request is not fixed
because I do not know how to duplicate the bug.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=429731
This could also be related to Support Request 685800
("Keyboard problem"). Apparently, on Spanish keyboards,
ALT-Gr+{ and ALT-Gr+[ don't work, but ALT-Gr+} and ALT-Gr+]
do work.
Perhaps we could figure out how to write some unit tests
simulating different keyboard layouts to demonstrate these
bugs on other platforms.
Logged In: YES
user_id=691516
I realized that I do not use meta keys on linux, so this
issue may apply to all systems with a meta key.
Logged In: YES
user_id=691516
I realized that I do not use meta keys on linux, so this
issue may apply to all systems with a meta key.
Logged In: YES
user_id=691516
I wrote a test that catches this problem. It is in a new
file, edu.rice.cs.drjava.ui.DefinitionsPaneTest However, I
still have no idea how to fix the problem. Perhaps the meta
key is not being registered somewhere as a modifier key. I
have not been able to findthe place where it should be if
this is the case.
Logged In: YES
user_id=429731
Take a look at KeyStrokeOption in the config package, and its accompanying test. There's already some things we have to deal with for ctrl/command and alt/option on the Mac. Meta might just have a different name we need to parse.
Logged In: YES
user_id=691516
Pressing a key combination like meta-a triggers a whole
series of KeyEvents. First is a KEY_PRESSED with keyCode of
KeyEvent.VK_META. Next is a KEY_PRESSED with keyCode of
KeyEvent.VK_A. If meta-a is bound to anything, this
KeyEvent will trigger the action. This event is not passed
by DefinitionsPane to super.processKeyEvent(...). Next comes
a KEY_TYPED with keyCode of KeyEvent.VK_UNKNOWN and keyChar
of "a". This is the event that triggered the extraneous
input in super.processKeyEvent(...), so I rewrote
DefinitionsPane.processKeyEvent(...) to throw away these
KeyEvent's. After the KEY_TYPED, there are KEY_RELEASED
events for "a" and meta symmetrical to the KEY_PRESSED
events, if anyone cares. You can see an example in
DefinitionsPaneTest.testMetaKeyPress().
So bottom line, I am closing this bug, because the original
bug is fixed. The alt-graph+{ support request is not fixed
because I do not know how to duplicate the bug.