Re: [VirtualGL-Users] Bug in TurboVNC v1.2.80 (build 20130919)

2013-10-23 Thread DRC
I guess I should have really learned by now to stop second guessing myself. Upon further examination, the reason why the firstUpdate mechanism is there is because there may be circumstances under which a user leaves their 3D application running and then reconnects to the TurboVNC Server

Re: [VirtualGL-Users] Bug in TurboVNC v1.2.80 (build 20130919)

2013-10-08 Thread DRC
Whew. So, for starters, I confirmed the behavior you're observing, but to figure out why it's happening required trolling the commit logs from a few years back. ALR used to be implemented using a second thread, which would wake up every 100 milliseconds, iterate through all of the active

Re: [VirtualGL-Users] Bug in TurboVNC v1.2.80 (build 20130919)

2013-10-04 Thread DRC
The default is for ALR to affect only PutImage operations, which is what VGL uses to draw images. Many 2D apps use other methods to draw images, like X Render or CopyArea, that won't be subject to ALR unless you set TVNC_ALRALL. The docs go into more detail. ALR is really targeted at 3D apps.

Re: [VirtualGL-Users] Bug in TurboVNC v1.2.80 (build 20130919)

2013-10-04 Thread DRC
I'm not in front of the code right now, but I'll double check the logic when I get a chance. I recall that I do things a little differently on the first refresh, but I can't recall the specifics. On Oct 4, 2013, at 4:24 PM, Kevin Van Workum v...@sabalcore.com wrote: OK, that makes sense.