I apologize for my "czech english", but I have problem with F10key processing on w2k, wxPython 2.6.3.2, python 2.4.3.
When I run the wxPython demo and try the KeyEvents demo I have noticed an odd behaviour when I press the F10 key.
The first KeyPress seems to be ok - WxPython catch KeyDown, char and KeyUp descriptors, but any key on keyboard does'n work until I press the F10 key again! After second press wxPython catch only KeyUp event and other keys works then again.
I apologize for my "czech english", but I have problem with F10key processing on w2k, wxPython 2.6.3.2, python 2.4.3.
When I run the wxPython demo and try the KeyEvents demo I have noticed an odd behaviour when I press the F10 key.
The first KeyPress seems to be ok - WxPython catch KeyDown, char and KeyUp descriptors, but any key on keyboard does'n work until I press the F10 key again! After second press wxPython catch only KeyUp event and other keys works then again.
Is it only my problem or is it a wxPython bug?
This is normal. F10 is a hot key for activating the menu bar, so since it appears that the app is not handling the key at all (the event handlers call event.Skip()) then Windows is shifting the focus to the menu bar. If you press 'f' then you will see the File menu dropped down. When the next F10 happens then Windows shifts the focus back to the window that had it before.
ยทยทยท
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!