Subject: Re: Stupid wsdisplay color question
To: Martin Husemann <martin@duskware.de>
From: Michael <macallan18@earthlink.net>
List: tech-kern
Date: 04/26/2005 07:45:47
--Signature_Tue__26_Apr_2005_07_45_47_-0400_ELeyTqgut4FzDHDl
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Hello,
> options WS_DEFAULT_FG=3DWSCOL_BLACK
> options WS_DEFAULT_BG=3DWSCOL_WHITE
> options WS_KERNEL_COLATTR=3DWSATTR_HILIT
> I would have exepected this to generate
>=20
> - white background
> - black text
> - kernel text the same, but bright (not dim)
>=20
> but what I get is (suprisingly?) quite different:
>=20
> - kernel text is dim gray on white background
WSATTR_HILIT adds brightness so that's normal
> - default text is white on black
Umm, which driver? Might be a bug although I'm pretty sure mine handle this=
correctly...
Might be
allocattr(ri, 0, 0, 0, defattr);
instead of=20
allocattr(ri, WS_DEFAULT_FG, WS_DEFAULT_BG, 0, defattr);
These should be equivalent according to the docs ( both foreground and back=
ground zero should give the default attribute ) but as far as I can tell th=
ey aren't, the default allocattr always defaults to PC-like grayish on blac=
k, no matter what WS_DEFAULT_* say.
have fun
Michael
--Signature_Tue__26_Apr_2005_07_45_47_-0400_ELeyTqgut4FzDHDl
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (NetBSD)
iQEVAwUBQm4p68pnzkX8Yg2nAQJmHgf/cCvPUzjNLih3+fg9beZ7U2O72HqWAvek
sbjpqfgJbBNEczvLtyVK/T0Yvnb6Ad7YZqngzXawN4H5IcZlCJLcbrZtcnZR2kUm
+HSWJ9kUXAthe4CNZu94keBZfx0Cy+ydQJcdlKCGGXktPsokq3OOBoqDzaEO29Qb
G+p71G1OCV+BhJBHUEjliUf7kuCj/l07ehVIZi/77b8EvKyYkBC4KGbh7Bj1hTVt
QQoBZQHO6eNHIcABe9gyojj8Q3Cy2//tQsFUl5D3RsmgzAOv9CmbeVnqQ4rO9PV5
v1+PWFVA7L9l7Vyf8mqw7dyLMnQ68n/kNdcLCc1x6IttbveGfXEw5A==
=KIGK
-----END PGP SIGNATURE-----
--Signature_Tue__26_Apr_2005_07_45_47_-0400_ELeyTqgut4FzDHDl--