How to store a stack in a custom property
Joe Lewis Wilkins
pepetoo at cox.net
Mon Apr 27 02:59:45 EDT 2009
Jim, thanks for the comments. I'm sure they will help someone.
On Apr 26, 2009, at 9:12 PM, Jim Bufalini wrote:
> - Have you ever found the need to create variables on-the-fly? Ones
> that are
> not declared in your code? Rev arrays allow for this and custom
> are "persistent" arrays that retain their values (provided you save
> stack) from one session to another. Array values are lost when the
> - Have you ever had the need to not write a stack to disk, usually for
> security reasons? Since locked stacks stored in custom properties
> can be
> launched only into memory and run, they are much harder to hack.
> - Have you ever had the need to know when a variable changes in
> memory due
> to a user initiated action? Custom properties allow for this.
> - Do you use globals? Custom properties allow for the creation of on-
> You probably use invisible fields and controls to store persistent
> information in your stack. Custom properties, however, are a much more
> sophisticated and flexible way to store information in your stack,
> any kind of information can be stored, it's in an array format, and
> don't have to create a bunch of invisible fields or other objects to
> this information.
> There are actually many more uses, and I personally don't know if I
> live without custom properties. ;-) The above are just a couple that
> have to do with writing data to a disk stack.
> Aloha from Hawaii,
> Jim Bufalini
More information about the use-livecode