|
From: <pe...@ce...> - 2003-01-02 13:30:33
|
On 21 Dec 2002, Constantin Kaplinsky wrote: > p> 1) Flickering. When moving the cursor, it flickers a lot. >=20 > I think this is because now TightVNC draws the cursor on the > framebuffer, instead of re-shaping native X pointer. Why is it necessary with a software cursor? Is it: 1) the need for double cursor (both the dot and the real one)? and/or 2) to be able to watch the cursor, even when another X11 window has focus= ,=20 eg. without having to move the real X11 cursor? For 1), i don't want the dot anyway.=20 For 2), wouldn't it be possible to use a software cursor when the viewer window hasn't focus, but use the real X11 cursor when it has focus? Also,= =20 this is not a problem in fullscreen mode.=20 > p> 2) The cursor dot: I don't want it. >=20 > 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. >=20 > 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. This is all nice, but my problem now is that our customers aren't accepting either flickering cursors or the extra dot. We are currently forced to patch vncviewer to the 1.2.4-style.=20 Would it be possible to add options for configuring this? I can probably=20 help with writing the code needed.=20 --=20 Peter =C5strand Telephone: +46-13-21 46 00 Cendio Systems E-mail: pe...@ce... Teknikringen 3 583 30 Link=F6ping |