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 weeble
Recipients Somelauw, ajaksu2, gpolo, weeble
Date 2009-01-24.20:49:27
SpamBayes Score 0.0004461383
Marked as misclassified No
Message-id <1232830168.46.0.835920101162.issue4676@psf.upfronthosting.co.za>
In-reply-to
Content
Another complication. On Windows, this line doesn't do what it claims:

if (event.state & 12) != 0 and event.keysym == "Home":
    # state&1==shift, state&4==control, state&8==alt
    return # <Modifier-Home>; fall back to class binding

The comment says state&8==alt, but this is wrong. state&8==mod1, and on
Windows Tk defines mod1 to be num-lock. So if you have num-lock on,
home_callback will always fall back to the standard binding.

See the Tk source:
xlib/X11/X.h   defines Mod1Mask
win/tkWinX.c   maps VK_NUMLOCK to Mod1Mask
History
Date User Action Args
2009-01-24 20:49:28weeblesetrecipients: + weeble, ajaksu2, gpolo, Somelauw
2009-01-24 20:49:28weeblesetmessageid: <1232830168.46.0.835920101162.issue4676@psf.upfronthosting.co.za>
2009-01-24 20:49:27weeblelinkissue4676 messages
2009-01-24 20:49:27weeblecreate