• 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
Scripting and objectSpecifier issue
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Scripting and objectSpecifier issue


  • Subject: Scripting and objectSpecifier issue
  • From: Joseph Jones <email@hidden>
  • Date: Fri, 01 Oct 2004 20:24:10 -0700

I am trying to make my app scriptable and I have run into a loggerhead.
Basically, if I try to stash one of my objects into an AS variable and user
it later I get an AS error stating that the command can not be created. If I
look into the event log for AS I see that the name of my class is <<class>>
id XXXXXX instead of projectitem id XXXXXX. When I turn CocoaScripting debug
output on, it appears that the want keyword is holding a NULL value
(0x00000000) instead of "Pitm" which is the code for the class I am trying
to use.

I am building an NSUniqueIDSpecifier to describe my class and I can't figure
out why it is showing the class as <<class>>. The two parents in the
containment hierarchy both override objectSpecifier and both parents can be
stored and retrieved ( as document id XXXXXX and project id XXXXXX ).

I am at my wits end here. I searched the archives for this bit haven't
located what I need to figure this out. The best advice I've seen is to
implement objectSpecifier, which I have done.

Can anyone enlighten me as to what I am doing wrong (or need to do) to
resolve this?

Thanx,
Joe


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Scripting and objectSpecifier issue
      • From: Dustin Voss <email@hidden>
    • Re: Scripting and objectSpecifier issue
      • From: Joseph Jones <email@hidden>
  • Prev by Date: Re: Limiting notifications to one document
  • Next by Date: Re: Binding/KVC : implicit and explicit invocation of description method
  • Previous by thread: Re: Binding/KVC : valueForKey: and NSDictionary (was: valid accessor for framework objects. (was: implicit and explicit invocation of description method))
  • Next by thread: Re: Scripting and objectSpecifier issue
  • Index(es):
    • Date
    • Thread