On Fri, Jun 29, 2012 at 10:00 AM, Pierre Ossman <oss...@cendio.se> wrote:
>
> The fact that your patch fixes something is an indication that we are
> overlooking some screen updates somewhere else. Unfortunately it's not
> really trivial to figure out what and where. You have to find a simple
> test case, and then start following the chain of draw commands and see
> where a hook is either missing, or miscalculating the damaged region.
>
I put some debug print statements in and it seems to either in
vncHooksPolyRectangle or vncHooksPolyFillRect (oddly, RHEL5 seems to call
PolyRectangle and Fedora 16 calls PolyFillRect). It would make sense for
it to be PolyRectangle since it's clearly the outlines of 1px wide boxes
that are not being drawn, but after comparing to the TurboVNC (which
doesn't exhibit the same problem) source code I have have not been able to
figure out what's going on. I noticed that every once in a while interior
box outlines are drawn, but never the outermost outline for a given window
or box. Requesting a screen refresh from the client causes everything to
be drawn correctly until some part of the outline is damaged and then that
area is not re-drawn correctly unless another refresh is requested.
-brian
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
