Bug#253280: gtk2-engines-industrial: problems with new xcursors default

ROBERTOJIMENOCA ROBERTOJIMENOCA <ROBERTOJIMENOCA@terra.es>, 253280@bugs.debian.org
Fri, 14 Jan 2005 11:32:32 GMT


Josselin Mouette wrote=3A
=3E Le mar 15/06/2004 =E0 16=3A40=2C ROBERTOJIMENOCA a =E9crit =3A
=3E =3E =3E Note that you can probably work around the first by disabling=
 the
=3E =3E =3E hardware cursor feature=2C
=3E =3E =

=3E =3E Why would someone that doesn=27t care about pretty cursor themes =
would
=3E =3E like to disable the hardware cursor feature=3F
=3E =3E I don=27t like hardware cursor disabled because that makes the cu=
rsor
=3E =3E blink when something changes in the background (indeed=2C that=27=
s why
=3E =3E hardware cursor was invented)
=3E =

=3E Is it also true of alpha cursors=3F I think they are displayed using =
the
=3E RENDER extension=2C not the hardware cursor mechanism=2E

sis=2C ati and nv xfree86 drivers support ARGB HW cursors

=3E =3E =3E and that you can also disable this cursor theme
=3E =3E =3E by using update-alternatives --config x-cursor-theme=2E
=3E =3E =

=3E =3E Should at least this cursor theme not be set by default=3F
=3E =

=3E Sorry=2C but if I back out this change I=27ll get hanged=2E Many user=
s were
=3E asking for a nice yet neutral default cursor theme=2C which is exactl=
y
=3E what Industrial is=2E Why should I deprive other users from a decent
=3E default theme because of a bug in some hardware=3F Why not fix the bu=
g in
=3E the hardware before=3F

Not every driver supports ARGB cursors (I only see sis=2C ati and nv)
So maybe the cards support ARGB cursors but the driver is not updated=2E

I also prefer the pretty cursors but it=27s more important for me using
the hardware accelerated cursor=2E

Maybe a good default would be to always use HW cursor and if there=27s no=

support for ARGB cursor use the not alpha cursors=2E
Would you default to that=3F