Game Development Community

OS-X Quit Menu when triggered from KB issue

by Chris Dillman · in Torque Game Builder · 04/13/2005 (7:51 pm) · 4 replies

OS-X Quit Menu when triggered from KB issue.

When you trigger the quit command from the KB
The menu flashes.

But the App does not respond and actually quit unless you hold down the
keys that trigger the quit command for a while.

Anyhow my first thought is events are not being handled correctly?
Or quit keys are not checked often enough?

Any thoughts?

I have not looked at the carbon event loop yet.

And Im not yet sure where in the engine menus are actually handled anyhow.
NextNext Thread
PrevPrevious Thread
More from Torque Game Builder


Torque Owner Matt Van Gorkom
#1
04/22/2005 (7:38 pm)
I've encountered this problem (every time) also. I've found that if you hold cmd-q down the T2D will quit.

Torque Owner Josh Williams
Default Studio Name
#2
04/23/2005 (12:02 pm)
Inputs are handled in the maccarb platform stuff. It definitely needs some clean-up and re-working. Input for basic things like reading gameplay keys (eg W-A-S-D) and taking mouse input works great, but modifier keys and OS X system keys are not very well supported in the core Torque OS X platform. Hopefully someone will fix this soon. I haven't had time to do this myself yet.

Torque Owner Chris Dillman
#3
05/26/2005 (1:43 am)
Ok I patched it.
I think this is a good fix...
Seems fine here in the debugger etc.

In file macCarbWindow.cc

Look for

case kEventAppQuit:
{
// !!!!!TBD -- we assume this only happens AFTER we posted a quit event...
break;
}

Change two...

case kEventAppQuit:
{
// !!!!!TBD -- we assume this only happens AFTER we posted a quit event...
Platform::postQuitMessage( 0 );

break;
}

Torque Owner Chris Dillman
#4
05/26/2005 (1:44 am)
BTW is there CVS for Torque?
Where I can directly patch things?