Richard,
In your script, it appears that a custom prop is dynamically declared
just by setting it's value? Is this all you have to do? In
SuperCard, one has to specifically declare a "user" property with a
"define" statement before ever setting it's value. Otherwise it
doesn't know if you are declaring a var or a prop... how does Rev do
this (oh, maybe it is the use of "set")?
Randall
On Jan 16, 2008, at 10:18 AM, Richard Gaskin wrote:
Thierry wrote:
Of course you have to replace spaces and slashes with some
string that will not break the name of the custom prop into
several parts :-)
Yes, I'm aware of that.
I think such failure depends on how it's done.
I just ran this test:
on mouseUp
put "some/thing" into v1
put "some thing" into v2
set the uTest[v1] of of this stack to "test"
set the uTest[v2] of of this stack to "test"
end mouseUp
...and it worked well, with "some/thing" and "some thing" appearing
among the lines of the customKeys of property set uTest, and I can
also retrieve their values with the same notation.
Does anyone recall the specific syntax which might cause this to fail?
--
Richard Gaskin
Managing Editor, revJournal
_______________________________________________________
Rev tips, tutorials and more: http://www.revJournal.com
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
