Mark Waddingham wrote:
> I still have a difficult time wrapping my head around the syntax for
> multiple custom property sets - especially since the introduction of
> nested arrays:
>
> http://quality.livecode.com/show_bug.cgi?id=6912
>
> ;)
This reminds me of a hypothesis I have that perhaps you can confirm:
When we use array syntax on custom property sets we have effectively a
sort of two-dimensional array. Would be nice to extend that deeper, but
I'll take what I get.
But when we put an array into a custom property value such as:
put "foo" into bar[1]
set the uBar of btn 1 to bar
...it seems we can store that even though it hasn't been explicitly
serialized.
So my hunch is that when we do that the engine is using the same
serialization it uses for arrayEncode, and when retrieving the array it
automatically runs it through the internal equivalent of arrayDecode.
Is that correct?
If not, by what sorcery are array values serialized when stored as
persistent property values?
--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web
____________________________________________________________________
ambassa...@fourthworld.com http://www.FourthWorld.com
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
