WinVNC

[Will Dean]

At 09:16 04/02/2000 -0600, you wrote:
>In a few postings lately it has been stated that WinVNC polls the entire
>screen for updates.

It only does this if you ask it to, or if the hooks go in.

>  Can someone explain where this is happening? When I
>look at the code I see the following in vncClient::TriggerUpdate()
>
>if (m_server->PollFullScreen())
>{
>         // do an update
>}

My source here is like this:

                 if (m_server->PollFullScreen())
                 {
                         RECT rect;
                         rect.left = (m_pollingcycle % 2) * m_qtrscreen.right;
                         rect.right = rect.left + m_qtrscreen.right;
                         rect.top = (m_pollingcycle / 2) * m_qtrscreen.bottom;
                         rect.bottom = rect.top + m_qtrscreen.bottom;

                         m_changed_rgn.AddRect(rect);

                         m_pollingcycle = (m_pollingcycle + 1) % 4;
                 }

What version is your source.


>Also, the timer use is also configured in the registry. Thus if
>prf_use_Timer is true and full screen polling is selected in the WinVNC
>user settings then I can see how this is happening. Am I mistaken with
>this? Out of the box, I just don't see how full screen polling is
>working. Any pointers are greatly appreciated.

Are you expecting it to poll full screen by default?  It doesn't.

You'll find that just to read the whole screen into RAM on a 
1280x1024x16bpp machine is over 200ms of work, even before you've looked 
for differences across the whole lot.  Polling the full screen is a very 
expensive thing to do to the server.

But I'm not sure I understand your question.

Will


---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to majordomo "at" uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------