Another possibility I ran into is to run the app as a launch agent
with a .app file in /Applications to allow the user to start the UI.
I created a plist for this and placed it into ~/Library/LaunchAgents,
then used launchctl to start it; once running, the .app file in /
Applications starts, finds the launch agent, launches a browser
pointed at the agent, and terminates as it should. Being a Mac
newbie, though, I'm not sure if this is a good way to allow users to
interact with applications - would this combined launch agent + app
approach be considered "appropriate" for Leopard and later?
If I do go the launch agent route, then I'll need to figure out how to
add my launchctl plist into ~/Library/LaunchAgents and get it started,
preferably without requiring a reboot. Can an installer post-
installation script run launchctl load? or is there a better way to do
it?
Thanks
Chris
On Nov 2, 2009, at 10:21 AM, Bill Janssen wrote:
I don't think you can launch an application more than once in a single
user context (LSMultipleInstancesProhibited is for multiple user
contexts). But you might try using the Java Web Start class
"javax.jnlp.SingleInstanceService" here...
Bill
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
