[ python-Bugs-1074333 ] input from numeric pad always dropped when numlock off

SourceForge.net noreply at sourceforge.net
Mon Dec 20 13:59:53 CET 2004


Bugs item #1074333, was opened at 2004-11-27 22:37
Message generated for change (Comment added) made by jlgijsbers
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1074333&group_id=5470

Category: IDLE
Group: Python 2.3
Status: Closed
Resolution: Rejected
Priority: 3
Submitted By: Rick Graves (netvigator)
Assigned to: Kurt B. Kaiser (kbk)
Summary: input from numeric pad always dropped when numlock off

Initial Comment:
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 am reporting this for Python 2.3, but I had exactly
the same problem in Python 2.2.

This problem has also been reported to RedHat, see 

http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136600.



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

>Comment By: Johannes Gijsbers (jlgijsbers)
Date: 2004-12-20 13:59

Message:
Logged In: YES 
user_id=469548

OP = opening poster. So yes, the ball is in your court. :)

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

Comment By: Rick Graves (netvigator)
Date: 2004-12-20 07:14

Message:
Logged In: YES 
user_id=1167414

> Yes, if OP wants to pursue it, he should take it up with the 
Tk people:   http://tcl.sourceforge.net/ 
 
1) Who is OP?   
 
2) Is this ball in my court or someone else's? 
 
Thanks, 
 
netvigator aka Rick Graves 

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

Comment By: Kurt B. Kaiser (kbk)
Date: 2004-12-20 00:13

Message:
Logged In: YES 
user_id=149084

Yes, if OP wants to pursue it, he should take it up with the
Tk people:   http://tcl.sourceforge.net/

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

Comment By: Raymond Hettinger (rhettinger)
Date: 2004-12-19 22:44

Message:
Logged In: YES 
user_id=80475

Kurt, as far as I can tell, there is nothing in Tkinter that
gives us any control over this.  If you concur, please mark
this as 3rd party and/or platform specific and close it.

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

Comment By: Rick Graves (netvigator)
Date: 2004-11-27 22:50

Message:
Logged In: YES 
user_id=1167414

In RedHat bugzilla, this problem was reported for fedora
under x86_64.  I have been having the problem on i386 using
CentOS-3, which is similar to RHEL 3.  So the problem seems
to apply across Linux architectures, but not across
platforms.  It may be a RedHat problem across architectures.  

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1074333&group_id=5470


More information about the Python-bugs-list mailing list