|
From: Constantin K. <co...@ce...> - 2002-12-21 10:22:03
|
Hello Peter, >>>>> "p" == <pe...@ce...> writes: p> I have some problems with the cursor in the X11 vncviewer: p> 1) Flickering. When moving the cursor, it flickers a lot. I think this is because now TightVNC draws the cursor on the framebuffer, instead of re-shaping native X pointer. p> I also notice that moving the cursor generates a lot of network p> traffic. Shouldn't TightVNCs local cursor handling prevent this? Most likely, this is outgoing traffic (sending pointer coordinates to the server). p> 2) The cursor dot: I don't want it. p> Both these problems appeared between TightVNC 1.2.4 and 1.2.5, it p> seems. When reading the source, I notice that 1.2.5 introduced a p> "software cursor", drawing on the FB, instead of using a X11 p> cursor. Why was this done? It feels like a step backwards. No, it's definitely a step forward. It's not correct to ignore the fact that there are two cursor positions: local and remote. Before 1.2.7, local cursor implementation simply ignored remote cursor position, but current version can both handle cursor movements locally, and display cursor movements performed either locally on the server or by other connected clients. -- With Best Wishes, Constantin |