Date: Thu, 27 Jun 1996 14:04:21 +0200 (MET DST) From: sos@FreeBSD.ORG To: ache@nagual.ru (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=) Cc: sos@FreeBSD.ORG, andreas@klemm.gtn.com, current@FreeBSD.ORG Subject: Re: Syscons 8bit chars mouse paste fix Message-ID: <199606271204.OAA06010@ra.dkuug.dk> In-Reply-To: <199606271134.PAA00575@nagual.ru> from "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" at Jun 27, 96 03:34:36 pm
next in thread | previous in thread | raw e-mail | index | archive | help
In reply to =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= who wrote:
>
> > Yes this is an artifact of how the mousepointer works, its the
> > chars D0-D3 actually, what you see must be because of your
> > scrmap. There is no fix for this, other than changeing the
> > involved chrs, just tomove the problem to another place. I chose
> > D0-D3 as they seemed to conflict the least in the charsets
> > that I use. Also the chars must be in the range that gets
> > bit 7 copied into bit 8 on 9 bit wide resolutions, which further
> > limits the available range.
>
> I know that 4 characters must be dead for mousepointer, but they
> must be choosed in _per-charset_ basis and scrnmap must be counted
> too. It can be moused option or maybe put this info into
> keymap table?
HMMM, it can't be a moused option, as it has (and shouldn't have)
no knowledge of whats going on on the screen.
Also it cannot be any chars, it HAS to be in the range that the
hardware supports the 9'th bit thingy (thats some 32 chars, I don't
remember the actual numbers, something like 0xd0-0xef).
HMMMM, I'll have to think about this one....
The problem with scrnmap on cut'ed text is solvable by having a
reverse scrnmap table..
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team
So much code to hack -- so little time.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606271204.OAA06010>