• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: What happens to additionalEventParamDescriptor?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: What happens to additionalEventParamDescriptor?


  • Subject: Re: What happens to additionalEventParamDescriptor?
  • From: has <email@hidden>
  • Date: Wed, 11 Apr 2007 11:31:30 +0100

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:additionalEventParamDescripto r:launchIdentifiers:], the NSAppleEventDescriptor that I pass for additionalEventParamDescriptor: seems to go into a black hole.

Looks broken; - launchAppWithBundleIdentifier:options:additionalEventParamDescriptor:lau 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
--
http://appscript.sourceforge.net
http://rb-appscript.rubyforge.org
http://appscript.sourceforge.net/objc-appscript.html

_______________________________________________

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


  • Prev by Date: Re: Tooltip font size again ...
  • Next by Date: Detect System Idle?
  • Previous by thread: What happens to additionalEventParamDescriptor?
  • Next by thread: Re: What happens to additionalEventParamDescriptor?
  • Index(es):
    • Date
    • Thread