Re: Scripting and objectSpecifier issue
Re: Scripting and objectSpecifier issue
- Subject: Re: Scripting and objectSpecifier issue
- From: Joseph Jones <email@hidden>
- Date: Fri, 01 Oct 2004 21:29:15 -0700
OK, I think I figured it out. It appears that the key returned in the object
specifier is dependant on who is calling for it. I used some knowledge in
the class itself to determine the key that needs to be returned.
Funny thing is that the second key being used in the specifier is the plural
form of the items type. ObjectSpecifier is being called on a "project item"
that is part of an elements key in my sdef file. I was trying to return the
specifier as a "project item" but only got it working when I returned it as
a "project items".???
Now I have a deeper question. It may come to a point where the limited
information I have at the time the objectSpecifier is called does not
provide enough information to make this decision. Is there any way to know
at the time the method is called any info I could use to determine the
correct key?
Thanx,
Joe
On 10/1/04 8:24 PM, "Joseph Jones" <email@hidden> wrote:
>
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
>
_______________________________________________
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