That post only applies if you are trying to do this from processes
that don't have access to the window server's higher level
functionality. The post you linked is talking about a CUPS filter
which runs as part of the printing process, but it (and any filters
it runs) run as background applications that are restricted in the
way they can use the window server.
To really understand what's going wrong with your application, we'll
need to know a lot more about what is going on when this isn't
working.
Well, maybe my app doesn't have access to the window server's higher
level functionality. Do command-line tools have access to it? What
distinguishes formally a Carbon command-line tool from a Carbon
application?
What the application does is the following, don't know if it helps…
1. Do various Gestalt calls to check the working environment
2. Read in some resources: MBAR, MENU and STR /STR#
3. Check for a licence file
3a. Display this warning if it is not found, and quit
3b. Create the main window (via YAAF framework calls)
and run the event loop.
3a is now a problem, because the call to StandardAlert() never
returns, seemingly because I can click the OK button. So it fails at a
very early stage in the application.
Does this additional information help?
J.P. _______________________________________________
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
