From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Tue,  7 May 2013 16:19:05 -0400
To: 9fans@9fans.net
Message-ID: <c64e36a5c61e19312ec130107bef9579@ladd.quanstro.net>
In-Reply-To: <e9d931072c26e2fdc231fef1408c0ab0@coraid.com>
References: <CAG3N4d-RfCYem-Ye_HvJnEBxUojUGFzoG4s2JUQO-O2Qfv233A@mail.gmail.com>
	<031b7fdd9ab256d19a5c9da921495f73@kw.quanstro.net>
	<9EB7F856-7F2C-4E05-8A15-935E3BBCA06F@gmail.com>
	<e9d931072c26e2fdc231fef1408c0ab0@coraid.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: 57bc16c2-ead8-11e9-9d60-3106f5b1d025

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

i read wrong.  i think this may fix the issue in a systemic, but not
entirely satisfying way.  it does seem rather optimistic that we can
just scribble on the screen.

    Top:
	dl = dst->layer;
	if(dl == nil){
		/* call memdraw so that hwdraw gets called */
		tmp = allocmemimage(r, dst->chan);
		n = loadfn(tmp, r, data, n);
		memdraw(dst, r, tmp, r.min, nil, r.min, S);
		freememimage(tmp);
		return n;
	}

by the way, hz should have nothing to do with it since i'm
using cinap's technique of a mouse process that redraws the
cursor when asked, or every 20ms, whichever comes first.

- erik