Roger (over and out!)
Message: 2 From: "Jyrki Kanerva" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Subject: Re: Launch Command Date: Wed, 19 Mar 2003 19:43:55 +0200 Reply-To: [EMAIL PROTECTED]
Just a guess, but try "/Macintosh HD/Applications/TextEdit.app" (first char is a slash before the drive name).
Regards,
Jyrki K
Message: 11 Date: Wed, 19 Mar 2003 10:26:24 -0800 Subject: Re: Launch Command From: Richard Gaskin <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED]
Jyrki Kanerva wrote:
Just a guess, but try "/Macintosh HD/Applications/TextEdit.app" (first char is a slash before the drive name).
Since we're talking about OS X, remember that Apple added one more way in
which the OS differs from how all other OSes work, in this case by deceiving
the user:
In most cases, a *.app appears to be - and by default acts like - a file,
but it is not. It is a folder, inside of which may be any number of other
files and folders.
With TexEdit, if your .app is at the location given above the path to the
actual executable is:
/Macintosh HD/Applications/TextEdit.app/Contents/MacOS/Tex-Edit Plus.Carbon
The name of the actual executable can be obtained from parsing the .plist
file within the bundle.
When writing code to launch apps, this latest Apple anomaly requires you to
special-case an exception for OS X; in all other OSes, a file is a file and
a folder is a folder, including Mac Classic (pre-CarbonLib).
-- Richard Gaskin Fourth World Media Corporation Developer of WebMerge 2.2: Publish any database on any site
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
