Sorry, I should have provided more information on the project. I'm working
as a graduate student and the project is a low cost dynamic tiled display
using laptops. Each laptop connects to a portion of a large VNC session. A
picture (dynamicwall_image.png) of an example that uses 15 macbooks to make
I doubt that the CUT would help in either case, because what it's really
filtering out are duplicate framebuffer updates. In the case of the CAD app
that is using single buffered drawing, each layer probably represents a
separate FBU, and thus the back-to-back FBU's aren't the same, even though
I have several apps that repaint the same area of the screen repeatedly.
I'm not sure if this is a case where ComparingUpdateTracker would be used,
but they are all IC CAD tools that draw a bird's eye view of the individual
layers (here's and example screenshot: http://www.mbeckler.org/cadence_plo
On Thu, 1 Sep 2011, Pierre Ossman wrote:
Have you done any research to validate the usefulness of the
ComparingUpdateTracker? Personally, I found that, in Xvnc, it wasn't
catching very many duplicate updates, and the dupes it was catching
would not have significantly slowed down performance (t
On Wed, 31 Aug 2011 09:54:26 -0600
DRC wrote:
> Have you done any research to validate the usefulness of the
> ComparingUpdateTracker? Personally, I found that, in Xvnc, it wasn't catching
> very many duplicate updates, and the dupes it was catching would not have
> significantly slowed down p
Have you done any research to validate the usefulness of the
ComparingUpdateTracker? Personally, I found that, in Xvnc, it wasn't catching
very many duplicate updates, and the dupes it was catching would not have
significantly slowed down performance (they tended to be areas of solid color,
whi
I was working on a project for school that included implementing a
multithreaded version of the ComparingUpdateTracker class to try and improve
overall performance. There are a couple things I was unsure about. I'm not
sure how the THREADED flag should be set as well as the THREADPOOL_SIZE
constant
