OSX ctrl-q key issues

[Gerald Brandt]

Hi,

Since upgrading to Mavericks I've had an issue with my application. My
application catches ctrl-q. Previous to Mavericks, I'd hit ctrl-q and
everything would be fine. Now I have to press ctrl-q twice in order for
my application to catch it.

I'm not sure if anything changed in Mavericks. I'm running trunk. Has
anyone else seen this issue?

Gerald
--
Gerald Brandt
Majentis Technologies
204-229-6595
***@majentis.com

[Stefan Csomor]

Hi Gerald

Post by Gerald Brandt
Hi,
Since upgrading to Mavericks I've had an issue with my application. My
application catches ctrl-q. Previous to Mavericks, I'd hit ctrl-q and
everything would be fine. Now I have to press ctrl-q twice in order for
my application to catch it.
I'm not sure if anything changed in Mavericks. I'm running trunk. Has
anyone else seen this issue?

a few thoughts

are you catching ctrl-q or command-q ? what is wrong with using the
built-in handling of these ?

I have to supply the menus on cocoa, and the quit command is getting the
expected shortcut of command-q, which is then mapped to wxID_EXIT. This
then is issuing a OnQueryEndSession and OnEndSession on the app instance.
The default handlings of these close the top window. Which might quit the
app (depending on ExitOnFrameDelete).

One situation where this still wouldn't quit the app immediately is if
this is happening in an inner event loop, so even if the ExitMainLoop was
called, this would need another event at the outer loop to really quit the
app.

Best,


Stefan

[Gerald Brandt]

Post by Stefan Csomor
Hi Gerald

Post by Gerald Brandt
Hi,
Since upgrading to Mavericks I've had an issue with my application. My
application catches ctrl-q. Previous to Mavericks, I'd hit ctrl-q and
everything would be fine. Now I have to press ctrl-q twice in order for
my application to catch it.
I'm not sure if anything changed in Mavericks. I'm running trunk. Has
anyone else seen this issue?

a few thoughts
are you catching ctrl-q or command-q ? what is wrong with using the
built-in handling of these ?
I have to supply the menus on cocoa, and the quit command is getting the
expected shortcut of command-q, which is then mapped to wxID_EXIT. This
then is issuing a OnQueryEndSession and OnEndSession on the app instance.
The default handlings of these close the top window. Which might quit the
app (depending on ExitOnFrameDelete).
One situation where this still wouldn't quit the app immediately is if
this is happening in an inner event loop, so even if the ExitMainLoop was
called, this would need another event at the outer loop to really quit the
app.
Best,
Stefan

I'm catching ctrl-q. My app stays away from any of the command-
sequences. The key sequence isn't even getting into my onChar() handler
until the second ctrl-q.

I see the same thing happening in the text sample. Just use the
textedit control, and the log window will display 'text changed in some
control' for every second ctrl-q entered.

In my app, ctrl-q is NOT tied to exit: http://wordtsar.ca



Gerald
--
Gerald Brandt
Majentis Technologies
204-229-6595
***@majentis.com