-
Bug
-
Resolution: Fixed
-
P3
-
1.0
-
1.0beta2
-
sparc
-
solaris_2.4
-
Not verified
95/11/12
This bug was originated by Bob Jervis. The bug has been sent to Sami Shaio
and has been answered by Sami.
[Bob Jervis]
7. Ctrl-A and Ctrl-End are still indistinguishable, as are Ctrl-D and Ctrl-Up
Arrow. The keystrokes for special keys need to generate values in a
different range from what they do.
[Sami Shaio]
Ctrl-End and Ctrl-Up are handed to you via the Event.KEY_ACTION id. I looked
at the code and it's a bug that keyDown is used for both normal keys and
action keys. In any case, when the id of the event is KEY_ACTION you
interpret the key field as:
Event.END or Event.UP
which happen to map to Ctrl-A and Ctrl-D. I suppose to make things clearer
I should change the constants so they don't collide.
================================================================
This bug was originated by Bob Jervis. The bug has been sent to Sami Shaio
and has been answered by Sami.
[Bob Jervis]
7. Ctrl-A and Ctrl-End are still indistinguishable, as are Ctrl-D and Ctrl-Up
Arrow. The keystrokes for special keys need to generate values in a
different range from what they do.
[Sami Shaio]
Ctrl-End and Ctrl-Up are handed to you via the Event.KEY_ACTION id. I looked
at the code and it's a bug that keyDown is used for both normal keys and
action keys. In any case, when the id of the event is KEY_ACTION you
interpret the key field as:
Event.END or Event.UP
which happen to map to Ctrl-A and Ctrl-D. I suppose to make things clearer
I should change the constants so they don't collide.
================================================================