These processes will have to communicate, and maybe one of
the signals would be something to tell the primary (transformed)
process to activate whenever any of the others is selected, to
fix the menu bar.
Anyway, the relevant APIs/methods are...
- [Processes.h] struct ProcessSerialNumber, GetFrontProcess(),
TransformProcessType() [10.3 or later]
- AppleEvents or some other inter-process communication method
like signals (kill(), "man 2 kill")
I like this idea from a stability point of view. It's really
ideal for the user...if anything happens to hang or crash a
window, the "application" would appear resilient to it. For
example, if I have 10 web browser windows open, why should 9 of
them disappear because one web site is adventurous and causes
problems for the browser?
Kevin G.
Even if you ditched Qt, in Carbon you'd find many of the same
restrictions.
You can make your app a "faceless background application" and the
first one to start can use TransformProcessType to become a
foreground app.
Your users might still notice some oddities—for instance, if the
user is in the Finder and clicks in the window for one of the
faceless background apps, the menubar will stay the Finder's,
because faceless apps (by design) do not have menubars. I think in
general this design is going to be a little goofy, UI-wise, no
matter how you slice it. But at the end of the day, if it really
does help performance, you might be willing to make that compromise.
On Oct 22, 2007, at 9:20 AM, Jeremy Friesner wrote:
Hi Scott,
Yeah, I know... the problem is that in this case most of the work
involved is the actual GUI updates themselves... and in Qt only
the main thread is allowed to manipulate GUI structures. If it
was just a matter of lots of calculations to do, I would do it in
a separate thread, but in this case it's updating audio meters,
creating/deleting/resizing widgets, etc.
-Jeremy
On Oct 22, 2007, at 8:30 AM, Scott Ribe wrote:
The "usual" way to do this is:
- multiple threads
- only the main thread updates the GUI
- worker threads send update events to the main thread
_______________________________________________
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/jstiles%
40blizzard.com
This email sent to email@hidden
_______________________________________________
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
This email sent to email@hidden
_______________________________________________
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
