joseph moore wrote:

Hello list, First off, if there is and easy way to display a paragraph of text in 3d

not "easy"

with GEM(as opposed to a single line) that's my main interest so lay it on me if one exists. My current approach is to use dyn~ to create however many text objects I need for a particular paragraph and space them out accordingly. So the current object I'm attemping to mass produce is simply this:

inlet | separator $1 | / text3d

why keep people thinking that [separator] could take an argument ? it does not!!! what is it supposed to do ? (or is my reading of this patch wrong ?)

I'm able to create multiple instances of the object, connect inlets, outlets, etc. But when I try to render I get the following message:

GEM: Start rendering dyn~: message unhandled - inlet:0 args:1 symbol:gem_state

I'm assuming that dyn~ handles messages and signals but not data from the GEM render chain?

from pd's point of view, a gem render chain is just a message (surprisingly it is a message with an identifier "gem_state")

probably [dyn~] can only pass "lists" (as opposed to anythings, like "gem_state" or "foo") ?

of course i am highly biased, but i (personally) would use something like zexy's [repeat]

[gemList( | [separator] | [repeat 5] | [translateXYZ 0 -1 0] | [text3d]

note that the [separator] has to be before the multiple instances of [translate]/[text3]

anyhow, this solution is rather under-optimal because of the problem that arises when setting the separate lines of text (reading from [textfile] might be a slow solution)- probably [dyn~] can handle this better...

mfg.asd.r IOhannes