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
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
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.
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.