This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author netvigator
Recipients
Date 2004-12-25.00:32:04
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=1167414

I posted the "bug" on the Tk list as suggested.  Today I got this: 
 
begin quote 
 
>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 
 
end quote 
 
Would  someone please either reopen this or let me know what my 
next step should be. 
 
Thanks, 
 
Rick 
History
Date User Action Args
2007-08-23 14:27:51adminlinkissue1074333 messages
2007-08-23 14:27:51admincreate