hello Iohannes
Le 07/11/2023 à 08:25, IOhannes m zmoelnig a écrit :
On 11/7/23 07:59, IOhannes m zmoelnig wrote:
i don't have an answer yet, but:
actually i think the problem is quite simple.
look like it was, since I can't reproduce it since your last commit!
thanks for confirming the bug and fixing it! cheers C
when banging a [gemhead] it doesn't ensure that the given openGL context is active. so if the single-buffer window isn't currently active, Gem is drawing "somewhere else". (i'm currently at a loss why it is drawing *at all*, that is: why does the single buffer window become active "sometimes" without being explicitly told)
i'm not sure about the actual solution though. should [gemhead] automatically ensure that the given context is active? (from a user perspective, the answer is probably a plain "yes"). or should there be an explicit message to [gemwin]? (similar to "bang" but without clearing the buffer)
mgfasdr IOhannes
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev