Date: Sun, 9 Apr 2017 08:23:55 +0300 From: Andrey Chernov <ache@freebsd.org> To: Bruce Evans <bde@FreeBSD.org>, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r316642 - head/sys/dev/syscons Message-ID: <23b8c635-f856-51b5-a338-d9bb53aefc7c@freebsd.org> In-Reply-To: <4a498d83-3b64-18ac-bb0f-890a0c2893fc@freebsd.org> References: <201704081000.v38A0dBU078784@repo.freebsd.org> <4a498d83-3b64-18ac-bb0f-890a0c2893fc@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 09.04.2017 7:54, Andrey Chernov wrote: > On 08.04.2017 13:00, Bruce Evans wrote: >> Log: >> Quick fix for removal of the mouse cursor in vga direct graphics modes >> (that is, in all supported 8, 15, 16 and 24-color modes). Moving the >> mouse cursor while holding down a button (giving cut marking) left a >> trail of garbage from misremoved mouse cursors (usually colored >> rectangles and not cursor shapes). Cases with a button not held down >> worked better and may even have worked. >> >> No renderer support for removing (software) mouse cursors is needed >> (and many renderers don't have any), since sc_remove_mouse_image() >> marks for update the region containing the image and usually much >> more. The mouse cursor can be (partially) over as many as 4 character >> cells, and removing it in only the 1-4 cells occupied by it would be >> best for efficiency and for avoiding flicker. > > Please don't forget that this 5 cells range (0xd0-0xd4, last one becomes > SC_CURSOR_CHAR) can be redefined with "vidcontrol -M", it is needed for > the case they overlap valid characters region for some code tables. Probably we just can change default to remove additional vidcontrol -M setup. I usually have this range started with 0x03.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?23b8c635-f856-51b5-a338-d9bb53aefc7c>