Closed GoogleCodeExporter closed 9 years ago
Setting style for wx.Frame:
style=(wx.DEFAULT_FRAME_STYLE | wx.WANTS_CHARS)
Original comment by czarek.t...@gmail.com
on 7 Aug 2013 at 4:55
See these links:
"Catching key events globally"
http://wiki.wxwidgets.org/Catching_key_events_globally
EVT_CHAR_HOOK
http://stackoverflow.com/questions/3876966/what-does-wxwidgets-evt-char-hook-do
"Unreliable keyboard events with wx.Frame"
http://comp.soft-sys.wxwindows.narkive.com/H0ymFpRo/unreliable-keyboard-events-w
ith-wxframe
Original comment by czarek.t...@gmail.com
on 7 Aug 2013 at 5:38
I think that the solution is to create the popup windows explicitilly, by
implenting the LifespanHandler.`OnBeforePopup` callback. Keyboard behaves
correctly in the wxpython.py popup example when using the NewWindow() function.
Original comment by czarek.t...@gmail.com
on 21 May 2014 at 7:34
Thanks, implenting the LifespanHandler.`OnBeforePopup` callback helped.
However this is not a straightforward solution as you can't create new window
directly in this callback (as it is executed in wrong thread).
Original comment by mathemat...@gmail.com
on 22 May 2014 at 2:21
Issue 61 is to allow posting tasks on the UI thread.
Original comment by czarek.t...@gmail.com
on 22 May 2014 at 2:31
Original comment by czarek.t...@gmail.com
on 22 May 2014 at 2:33
[deleted comment]
Fixed in revision a07c898cb1df.
Exposed cefpython.`PostTask` function for execution of tasks on various
threads. See example usage:
https://code.google.com/p/cefpython/source/browse/cefpython/cef3/windows/binarie
s/wxpython.py?r=a07c898cb1df#607
Original comment by czarek.t...@gmail.com
on 9 Aug 2014 at 4:18
[deleted comment]
Note that are implications of creating the popup window of our own by
implementing LifespanHandler.OnBeforePopup. The popup window and parent window
will not be able to script each other. There will be no "window.opener"
property available in the popup window.
Original comment by czarek.t...@gmail.com
on 22 Jan 2015 at 5:00
The popup/parent scripting issues are to be fixed in a separate Issue 171.
Original comment by czarek.t...@gmail.com
on 23 Jan 2015 at 11:42
Original issue reported on code.google.com by
czarek.t...@gmail.com
on 7 Aug 2013 at 4:47