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.
I use a lot of subchains with different textures...
I've had trouble making a test patch since the issue seems to only come up with a complex patch..
I'll try harder.
I've been pretty happy with the stability of the gem CVS stuff since I got it to compile thanks to Johannes. I can run a patch for a couple days (7300*12s at the moment)
.b.
IOhannes m zmoelnig wrote:
chris clepper wrote:
I put a build up that fixes the crash when QT load, has some of my more
fine.
recent pix_ objects and does ARB_ shaders. I also moved the QT init code into the GemMan init and added a fps output to gemwin (not checked into CVs
hmm, why don't we just use [realtime] in connection with a [gemhead]-trigger? this way we would not need to change anything in C - it is all there already (not that this is really a question and not even a suggestion...)
it would be great if you could check in your changes asap, esp. an updated project-file.
i would like to make a release whenever possible. any known open bugs, that are likely to be fixed within the next days?
the only bugs that come to my mind are:
- "external" window closing is likely to crash pd (linux)
- "destroy" sometimes hangs (cannot reproduce it, but i believe the
bug-report; i guess this is highly hw-dependent; linux)
- autoconf build-system on osX
-- certainly a lot of others which i have forgotten
i don't think that the window-crashes on linux are likely to be fixed before 0.91; i would like the osX-autoconf to work again, so if somebody could spare some time on that i would be thankful.
apart from that i would highly recommend a feature freeze right now.
what do you think?
mfg.asd.r IOhannes
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev