[PD] GEM - multiple geos - each accessable for transformation

[chun lee]

Hi peter:

Tried your patch and it makes sense. I was thinking of the similar thing. I
also found this patch on the list "[pd][Gem]Iterating geos tricks" which
uses writing to arrays to remember the location of each geo. And it looks
really nice;)

This is definitely interesting to look into more. Following your patch, one
idea will be creating the [pd tabwrite] dynamically according to the number
of cubes being drawn. So that each cube can adjust its own position.

Cheers

CHUN

>Try this one, based on tables, with each slot in a table corresponding to
>one cube.  Translator needs telling each individual time you want it to do
>something different, which means that your method of only sending in data
>when the counter ID matched the chosen object to move, meant that data would
>remain there for all the other cubes.  So instead, you can use your 'chosen
>for editing' number, to decide which slot in the tables to write to.  Then
>you read all of them back, every frame.   I hope that, and my attached
>example, make sense.
>
>Cheers,
>Peter