hi, the timing and erasing is usually done by the gemwin. afaik there is no way to get the erase trigger and the render trigger as two separate events from gemwin. what you probably have to do is erase the rendercontext manually by setting gemwin to singlebuffer(?) and then erasing the "window" with a bang to gemwin. I'm am just guessing here, but maybe do a [t b b b]: 1) bang to gemwin (erase old context) 2) bang to lua (free resources and then draw new) 3) bang to the gemhead for the gem renderchain do you have a working luagl version for os x? do you also have the problem that the gemwin doesnot come to the foreground? are you on mac at all? marius.
Wesley Smith wrote:
I don't know that much about shaders in Gem (my copy of Gem doesn't have the glsl stuff) , but I think I get what you're saying. So you are:
- Compiling and allocating a shader in the LUA script.
- Using that shader outside the lua script in some Gem stuff.
- Finished with the shader, but you don't know how to free it's
resources.
close but not quite
- Compiling and allocating a shader in the LUA script.
- Using that shader _inside_ the lua script
- Finished with the shader, but you don't know how to free it's
resources (this happens when the render window goes away ... I want that notification)
wes
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev