Twinkling display bug on Win8 laptop with AMD 7650M about vispy HOT 9 CLOSED

On all backends as well?

from vispy.

This might be related to the autoswap functionality that I added this weekend. If you remove the call to swap_buffers(), is the effect gone?

from vispy.

@lcampagn Ah, good idea. I just tried spinning cube with different backends:

• pyglet: same issue
• glut: works great
• qt: same problem

from vispy.

@almarklein yes! removing the call to swap_buffers makes it it work on all backends. So this issue does not occur on any of your computers?

from vispy.

I only tested on Linux. But all backends work ok. I was actually surprised, because I expected problems if you swap buffers twice.

Ok, so now we know that swapping buffers twice should be avoided. We could make Canvas.swap_buffers() only work if the autoswap flag is off, so that the examples would just work. But I think we should accept this "problem" and fix the examples as soon as we have a new release.

from vispy.

@rossant Can we close this?

from vispy.

Is the auto-swap thing fixed on all machines? I think someone had an issue
yesterday on Windows during the sprint?

2013/8/26 Almar Klein [email protected]

@rossant https://github.com/rossant Can we close this?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/25#issuecomment-23250234
.

from vispy.

Yeah, but the issue was that he was accidentally using an old installed vispy 0.1.0

from vispy.

Oh yes you're right! Anyway the examples work fine now, I guess we can close this.

from vispy.