[Tcl-bugs] [ tktoolkit-Bugs-1090719 ] input from numeric pad always dropped when numlock off

[SourceForge.net <no...@so...>]

Bugs item #1090719, was opened at 2004-12-23 22:14
Message generated for change (Comment added) made by hobbs
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=112997&aid=1090719&group_id=12997

Category: 69. Events
Group: None
>Status: Closed
>Resolution: Invalid
Priority: 5
Submitted By: Rick Graves (netvigator)
Assigned to: Jeffrey Hobbs (hobbs)
Summary: input from numeric pad always dropped when numlock off

Initial Comment:
In IDLE, the Python IDE (integrated development environment, 
written in Tk), the behaviour of the direction keys on the numpad 
is inconsistent when numlock is turned off.  
Home/End/PgUp/PgDn and the arrow keys work fine in some 
applications (gedit), but do not work in Python's IDLE. 
By not work, I mean: input is silently dropped. 
 
How reproducible: 
Always 
 
Steps to Reproduce: 
1. Turn off numlock. 
3. Open gedit, type in garbage, use direction keys on 
numpad to move around. 
4. Open idle, type in garbage, attempt to use direction 
keys on numpad to move around. It fails.     
 
Actual Results:  Intense frustration for people who 
have been using the numeric keypad as direction keys 
for decades! 
 
Expected Results:  When numlock is off, the direction 
keys on the numpad should function in the same manner 
as the dedicated direction keys. 
 
I reported this to Python, but they say it is a Tk problem, and 
that it is my responsibility to post the bug here.  Bugs item 
#1074333. 
 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1074333&group_id=5470 
 
This problem has also been reported to RedHat, see  
 
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136600. 

----------------------------------------------------------------------

>Comment By: Jeffrey Hobbs (hobbs)
Date: 2004-12-24 11:25

Message:
Logged In: YES 
user_id=72656

This is not a bug, but rather just that Tk differentiates
between the regular arrow up and keypad up on some systems,
depending on how their system keymaps operate.  The first is
<Up> and the second is <KP_Up> on Linux, but both are <Up>
on Windows.  This has always been the case for KP_Enter as
well.  The fact that Windows doesn't separate these is by
design, but has also caused people to want them separated
(see TIP http://www.tcl.tk/cgi-bin/tct/tip/158.html).

IOW, the bindings should be on <Up> and <KP_Up> if they are
to be considered equivalent in an app.  This is best handled
by using virtual events (like <<Up>>) and adding the
specific event names that you want to apply to it.  Please
filter this back to the other reports.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=112997&aid=1090719&group_id=12997