B. Bogart wrote:
hey all,
correct me if I'm wrong, but as long as there is no "symbol" in front of the atoms that get funneled into text3d, there is no memleak or filling up the symbol table, since we're not using symbols at all, just lists of atoms...
unfortunately i feel like having to correct you, since you are wrong.
the memleak occurs with symbol-atoms, not just with symbol-messages. a symbol-message is a message with the id (always a symbol-atom) "symbol" and the first argument being another symbol-atom of your choice.
Now that I think about it it may be hard to generate these non-symbols without converting them to symbols at ay point...
Maybe a string type should be higher on the PD list than a video/image type?
agreed, who volunteers? :-(
moocow has implemented a "numeric list-based string representation": the string is represented as a list of (decimal) ascii-values; the list's id is "string"; e.g. [string 102 111 111 32 98 97 114( is a representation of the string "foo bar"
Gem's [text]-objects understand and display these messages.
that's how i would do the "iterative text" with Gem.
fgma.dsr IOhannes