[ wxwindows-Bugs-1746376 ] Mouse Capture + wxLogGui => GTK+Gnome dies
SourceForge.net
noreply at sourceforge.net
Mon Jul 2 03:04:26 PDT 2007
Bugs item #1746376, was opened at 2007-07-02 12:04
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=109863&aid=1746376&group_id=9863
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: wxGTK specific
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: arst (arst)
Assigned to: Nobody/Anonymous (nobody)
Summary: Mouse Capture + wxLogGui => GTK+Gnome dies
Initial Comment:
When the wxLogGui instance receives logging and while a window has mouse capture, using wxLog functions then... brings down the whole Gnome GTK environment.
Nothing to do but to restart the whole desktop, because of the modal message box.
Apparently this is a 'feature' of GTK, once something has mouse capture, input cannot go anywhere else, and it's impossible to close the modal dialog. And, the whole desktop is dead also (even keyboard! [except some Ctrl-Backspace]).
I saw some Eclipse notes on the subject, they had made the experience that any mouse capture must be removed before showing a modal dialog.
So this is an oddity of GTK, but I think wxWidgets must check for this before showing a message dialog, since otherwise one has to do clever workarounds to avoid the problem.
Exactly the same problem is triggered by hitting a breakpoint in the debugger while some window has capture. But then it's outside wxW control.
Regards
// Arne S.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=109863&aid=1746376&group_id=9863
More information about the wx-dev
mailing list