Re: What happens to additionalEventParamDescriptor?
Re: What happens to additionalEventParamDescriptor?
- Subject: Re: What happens to additionalEventParamDescriptor?
- From: Steve Evangelou <email@hidden>
- Date: Wed, 11 Apr 2007 10:30:57 -0700
That's correct: openURLs:... isn't passing on the
additionalEventParamDescriptor parameter (and
launchAppWithBundleIdentifier calls through to openURLs:..). There is
a fix for this in Leopard, but go ahead and file a bug--if nothing
else, the documentation should be updated.
Steve
On Apr 11, 2007, at 6:38 AM, has wrote:
Date: Wed, 11 Apr 2007 11:31:30 +0100
From: has <email@hidden>
Subject: Re: What happens to additionalEventParamDescriptor?
To: email@hidden
Message-ID: <email@hidden>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
James Bucanek wrote:
I'm sending open AppleEvents to an application from a mixture of
Carbon and Cocoa [...]
However, when I used the (I thought) equivalent Cocoa call -
[NSWorkspace
openURLs:withAppBundleIdentifier:options:additionalEventParamDescript
o
r:launchIdentifiers:], the NSAppleEventDescriptor that I pass for
additionalEventParamDescriptor: seems to go into a black hole.
Looks broken; -
launchAppWithBundleIdentifier:options:additionalEventParamDescriptor:l
au
nchIdentifier: seems to have the same problem. All I can suggest is
to file a bug on 'em and stick to using LSOpenFromRefSpec in the
meantime. (Or you could try appscript, though it may be overkill for
this.)
HTH
has
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden