array info request (new thread)

[Dennis Brown]

Jonathan,

I can see why I have not had a problem.
I only set the customPropertySet in order to create a set or play  
with the keys.
I always set it back to empty immediately after (default)
Then I access the custom property only using array notation mySet 
["this and that words"]
I continue to access normal single custom properties as if no sets  
exist.

Using this method, I can keep everything straight in my mind,  
otherwise it can get confusing.

However, it seems to me that what you did should have worked.  Did  
you BZ this?

Dennis

On Jul 25, 2005, at 3:07 PM, Lynch, Jonathan wrote:

> I just tested this again, and the same problem shows up...
>
> Try clicking a button with this script:
>
> On mouseup
>   Set the custompropertyset of this stack to "my Set"
>   Set the myProp of this stack to "hello"
> End mouseup
>
> Then go look at the custom properties of the stack. When I do this, I
> have a custom property named "myProp" listed under the custom property
> set named "my set" - but I also have a custom property named myProp
> listed under the default custom property set. The first time I  
> click the
> button, "hello" is put in the myProp in the default set, and then the
> second time I click the button, "hello" is put in myProp in "my set".
>
> Weird stuff, but it goes away if the custompropertyset just has a
> one-word name.
>
> Besides, you need a one-word name if you are going to access it with
> array notation: put mySet["myProp"] into field "my field"
>