On Nov 2, 2007, at 9:06 AM, Dirk Stegemann (Mailing-Lists) wrote:
Without a running event loop, your mouse clicks and keyboard
commands are not processed -- somehow you have to start your event
loop (3b) before displaying the dialogue (3a).
Actually, the StandardAlert call runs the event loop itself. There's
no need for the app to run the event loop before calling StandardAlert.
J.P., does your app use the bundled directory format (YourApp.app/
Contents/MacOS/YourApp contains your binary), or are you just building
a single unbundled binary file? The symptoms you're describing are
typical of an unbundled app. Mac OS X requires an app to be bundled
for it to get the normal process management behavior for a GUI app.
If your app is unbundled, you can make it behave like a GUI app by
calling TransformProcessType (Processes.h) to make it foreground-
capable.
-eric
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
