Although I can appreciate your suggestion, I often have VNC running 
watching and waiting for something to happen on the remote screen to let me 
know that a task has completed. During this time, there is typically no 
mouse or keyboard activity. With your suggestion, I would never find out 
that a dialog box appeared on the screen.

Why not just stop the cursor from blinking, or at least reduce its blink 
rate down to the minimum? Assuming you stopped the blinking altogether, the 
down side would be that some dial-up users may find they loose their 
connection after a period of time of no data activity at all .

                         Michael Milette
                         ...also from Canada

At 09:08 PM 2003-01-14, Shing-Fat Fred Ma wrote:

>Here in Canada, many high-speed service providers are
>putting a monthly quota on the number of bits you can
>download before they charge you extra.  They refer to
>the quota as "bandwidth" (bits per month).
>
>People who are likely to use VNC and its variants are
>often not the same people who download Zigabytes of
>porn, video, and music.  So they might be able to live
>within the quota, even with extended VNC sessions.
>
>One of the features that really chew up quota is the
>blinking cursor that many applications have.  The
>bit-meter is constantly running.  I wonder
>if it would be easy enough to implement a smart scheme
>for screen updates?  That is, if there hasn't been pointer
>movement or keyboard events from the viewer for several
>minutes, there's no need to update the screen.  This is
>a bit like having the monitor go black when there has been
>inactivity for a while, except we're talking a vncviewer
>window instead of a monitor.  And it doesn't have to go
>blank, it just needs no updating.  There are probably many
>nondistracting ways to indicate to the user that the viewer
>is in this idle mode, without disrupting the viewer content
>too much.
>
>Does this sound like it would be generally useful, and
>do-able?  I don't know if I will ever have time to get up
>to speed on the kind of programming required, but maybe
>someone might get to it before me.  ;)
>
>Fred
>
>--
>Fred Ma, [EMAIL PROTECTED]
>Carleton University, Dept. of Electronics
>1125 Colonel By Drive, Ottawa, Ontario
>Canada, K1S 5B6
>_______________________________________________
>VNC-List mailing list
>[EMAIL PROTECTED]
>http://www.realvnc.com/mailman/listinfo/vnc-list
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to