On 5 Nov 2010, at 06:36, Jim Wintermyre wrote:
> 
> - I could turn on LSUIElement and always run the app in the background.  
> Whenever the app needs to display a window, it launches a separate proxy app 
> which shows up in the dock and app switcher. The purpose of this app is 
> solely to manage window focus issues.  So, to the user, it would appear that 
> any windows coming from my background app actually "belong" to this proxy 
> app. Whenever on of my windows is clicked on, I need to bring the proxy app 
> to the foreground, and then bring all my windows to the foreground. When my 
> app goes to the background, whatever windows the new foreground app has come 
> to the foreground as usual.  If the user then activates my app via the app 
> switcher or whatever, it would have to tell the background app to activate my 
> windows.  Basically this would be trying to kinda fake what the OS normally 
> does automatically. These kinds of hacks usually seem fraught with strange 
> bugs... but I don't have a better idea at the moment.
> 

To me it seems that to conform to your requirements your solution requires a 
faceless user space agent process and a regular gui management app.

Common code can be factored into a framework shared both by the agent and the 
app.
OS X and Cocoa are replete with IPC mechanisms - distributed notifications are 
simple to implement for low bandwidth situations.

If the code is a serious undertaking, rather than a hobby project, personally I 
would fix my design rather than expending intellectual effort on fragile 
hackology.

Regards

Jonathan Mitchell

Developer
Mugginsoft LLP
http://www.mugginsoft.com

_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to