From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@labs.coraid.com>
Date: Tue,  7 May 2013 14:54:04 -0400
To: 9fans@9fans.net
Message-ID: <e9d931072c26e2fdc231fef1408c0ab0@coraid.com>
In-Reply-To: <9EB7F856-7F2C-4E05-8A15-935E3BBCA06F@gmail.com>
References: <CAG3N4d-RfCYem-Ye_HvJnEBxUojUGFzoG4s2JUQO-O2Qfv233A@mail.gmail.com>
	<031b7fdd9ab256d19a5c9da921495f73@kw.quanstro.net>
	<9EB7F856-7F2C-4E05-8A15-935E3BBCA06F@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] vncv sw cursor trail
Topicbox-Message-UUID: 57b538fc-ead8-11e9-9d60-3106f5b1d025

On Tue May  7 14:51:13 EDT 2013, yarikos@gmail.com wrote:
>
> > the issue, and this fact this fix works must mean that
> > devdraw(3)'s 'd' command usually doesn't cause (much)
> > cursor flicker, but the 'y' command does.
> >
> > so either there is a timing or locking problem on the pi,
> > or swcursoravoid(r) is not called for the 'y' command.
>
> Correct: swcursoravoid is called from hwdraw; memdraw (the 'd' case) does call hwdraw, memload (the 'y' case) does not.
> Other programs avoid the issue because the programs do not load images directly to screen.

i think the assertion that memload "loads directly to the screen" is not correct.
at least to my walking through memload.

- erik