Aha! I can reproduce both of these. Now I see what you mean. You and
Trevor are talking about two different things.
Trevor is naming new property sets uniquely. The keys of these custom
property sets can be anything, but the actual name of the set itself
cannot be a reserved word. That's what you are trying to do in recipe
#2. The name of a custom property in the default set also cannot be a
reserved word. That's your recipe #1.
It isn't a bug, it's just how things work. When you say:
the name of btn 1
the engine cannot know whether you mean a custom property called "name"
or the built-in property -- and it is right to forbid that duplication.
Recipe #2 is an extension of the same thing, though I confess not to
know the exact details why. But it makes sense to me on a generic level.
Stephen Barncard wrote:
At 19:27 -0600 2/20/06, J. Landman Gay wrote:
I just did this:
set the cList["name"] of this stack to "testName"
put the cList["name"] of this stack
And got the expected result. Did I do the test right?
J. did you check to see if the stack name changed?
This does it every time in the Inspector:
recipe 1:
select an object
create new property set for the object
name it "name" (or any other object regular property without quotes of
course) in the entry box.
hit enter
and you get a dialog:
"a custom property set cannot be a property name"
recipe 2:
select an object
create new property for the object
name it "name*" (without quotes of course) in the entry box.
hit enter
and you will see the new property in the property list
but it's a lie... because the data is..... THE NAME OF THE OBJECT!!!
and no dialog....does that mean it's a bug?
this is MacOS Tiger 10.4.4 REV ENTERPRISE 2.7 Powerbook G4 1.33 GHZ
--
Jacqueline Landman Gay | [EMAIL PROTECTED]
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
