On Sat, Dec 13, 2008 at 5:28 PM, Iceberg-Dev dev.iceb...@gmail.com wrote:
On Dec 13, 2008, at 12:46 PM, Kyle Sluder wrote:
3) Why all this trouble of launching executables? There's a reason
Launch Services is a public framework; use that. Don't use
-[NSWorkspace openFile:], because that's
On Sun, Dec 14, 2008 at 2:03 PM, Michael Ash michael@gmail.com wrote:
Although it's only about ten more seconds of typing to use
-openFile:withApplication: instead and simply avoid the possibility
altogether.
If you're using this method, make sure to use -[NSWorkspace
Dennis,
You need to set the launch path of the executable within your NSTask -
currently you're passing /usr/bin/open as an argument to nothing.
There are two ways to do this: firstly, using the same logic you've
got below, you can have the launch path be a shell and pass /usr/bin/
open
An easier way may be to get NSWorkspace to do the work for you using
the openFile: message.
http://tinyurl.com/NSWorkspace
Mark
On 13 Dec 2008, at 11:01, Mark Allan wrote:
Dennis,
You need to set the launch path of the executable within your NSTask
- currently you're passing
Mark, there are a few things wrong with your advice.
1) Don't invoke a shell unless you need to. Doing so introduces far
too many variables to be useful for the simple purpose of launching
another executable.
2) The first argument to a program needs to be the name of the
program. For example,
On Dec 13, 2008, at 12:46 PM, Kyle Sluder wrote:
3) Why all this trouble of launching executables? There's a reason
Launch Services is a public framework; use that. Don't use
-[NSWorkspace openFile:], because that's not guaranteed to open the
package in Installer.app. Instead, use
I'm trying to distribute an installer within my own application bundle
in the resources directory and run it from my application. When I try
to run it from the debugger I get the error launch path not
accessible. However, if I then use the terminal to run the command
by hand using the
