>> They are _extremely_ limited with the current implementation.

>what do you mean by that?

* big resource hog-- you'll get dropouts with drawing instructions
or animations of any complexity
* you must choose between using $0 in struct name (for locality) or
having flexible approach where you can save/retrieve state.  (Unlike
a "Put" menu array where you can get both)
* no option to _not_ save ds state with the patch (Unlike a "Put" menu
array)
* buffer overflow when reading state from file http://sourceforge.net/tracker/index.php?func=detail&aid=1469910&group_id=55736&atid=478070
* cannot easily set hotspot for mouse manipulation
* hotspot bug http://sourceforge.net/tracker/index.php?func=detail&aid=2457992&group_id=55736&atid=478070
* flickering animation with arrays and/or lots of scalars on screen
* crashes with nested arrays when changing struct args
* many other problems

Usable for making a static score/diagram that will not be encapsulated inside an
abstraction, and for array manipulations that don't require any drawing instructions.
So _extremely_ limited.

-Jonathan