Hi Chris,
Indeed that is the problem, I'm often putting different textures on different subchains on a single gem-head (so I can control the render order of them both as a single object.)
Short of the suggestion of push and pop matrix from Cyrille, and simply not using separator and having pix_* and geo below where the chain splits, what is the "proper" method of texturing two subchains seperatly?
Or worse, having one subchain get a texture from above the separator, and a another subchain setting its own texture...
I apologize if it is already there, but I've still not seen any working examples of a "clear" message to gemwin to give single-buffer-like trails...?
I think now is a good time for a release indeed!
.b.
chris clepper wrote:
On 3/9/06, *B. Bogart* <ben@ekran.org mailto:ben@ekran.org> wrote:
I would very much like this separator for texture coords thing fixed. Either I get a memory leak or I have to remove separator and try and figure out whats going on.
The texture coordinates have to be created before other objects can modify them. pix_texture has to be first in the chain ahead of separator and pix_coordinate. I use separator with switching the gem chains around and avoid the leak. We could perhaps fix the number of texture coordinates to four and have the gemhead create them and never destroy them until the gemhead destructor.
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev