New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Single buffer issues #410
Comments
hi, just wanted to report that 'buffer 1' message for gemwin is not working as the old versions. untitled.mp4 |
Please test single buffer issues.pd.zip and report if it works for you. Weirdly enough I just tried with last deken version under MacOS (GEM: ver: 0.94.git v0.94-837-g56612c012) and I can draw using a bang to [gemhead] and also to [gem/gemhead] abstraction now... |
I downloaded again the last gem version from deken, and now it works like this, so it should be the right way, yes? but does this mean that in the past when I was switching from buffer 1 to buffer 2 and it was rendering everything like it's doing now, but with the metro triggering the gemhead, was a bug? becuase it was very usuful not to have to trigger all the gemheads in the buffer 1 mode, and to have the possibility to swtich between those modes on spot |
I note that triggering [gemhead] under MacOS single buffering actually draws, but returns a red error at every render:
Changing mode on spot is only possible since [gemglfw3window] is used as default, which allows many new message to be sent after windows creation. It's an interesting new feature yes, but then this message printed to the console is wrong and need to be removed:
|
I've fixed the as for the however, when creating a single-buffered window and then (attempt to) switch to double-buffered mode, the automatic-rendering¹ (by sending a for now, I've turned the warning into a one-shot warning (that is: it's only emitted the first time you try to switch the buffer mode). ¹ i think that @60-hz is right that (iiuc) that auto-rendering was not supposed to work in single-buffered mode. it does now. not sure whether this should be turned into a promise :-) PS: please don't use |
also note, that this error actually only appears (well: appeared) if you are mixing anyhow, it should be fixed. |
and this i couldn't reproduce (but i might have misunderstood the problem). |
The creation of a window in single buffer mode needs the buffer to be cleared once before use, otherwise its size is wrong. (The old behavior didn't need to manually clear buffer before using it).
Force rendering on [gemhead] doesn't work, but abstraction [gem/gemhead] can draw. (should be related to gemhead abstraction is not used, and the compiled object behaviors changed. #408)
MacOS with gemglfw3window, here is a simple patch to test:
single buffer issues.pd.zip
The text was updated successfully, but these errors were encountered: