After playing with Option "Overlay" with my G400, I think I know why most
apps only run on the default visual-- it's well nigh impossible to do
anything useful on the overlay visual.
It's a little annoying that the default visual is 8 bit PseudoColor and
there's no way to make it 24 bit TrueColor
On Fri, 9 Nov 2001, Jeremy wrote:
[...]
> The most annoying, however, has got to be dealing with the colormap on the
> PseudoColor visual. XCreateColormap() is happy to claim to give me a 256
> entry colormap, but, I'm assuming because of how the overlay works, entry 255
> (the topmost) doesn't
On Fri, 9 Nov 2001, Mark Vojkovich wrote:
> On Fri, 9 Nov 2001, Jeremy wrote:
>Contrary to some opinion on this list, overlays are not intended
> to make legacy PseudoColor apps work. Overlays in the X-window
> system are for layers of windows that don't clip other windows.
I'll accept that.
On Fri, 9 Nov 2001, Jeremy wrote:
> On Fri, 9 Nov 2001, Mark Vojkovich wrote:
> > On Fri, 9 Nov 2001, Jeremy wrote:
> >Contrary to some opinion on this list, overlays are not intended
> > to make legacy PseudoColor apps work. Overlays in the X-window
> > system are for layers of windows that
On Fri, 9 Nov 2001, Mark Vojkovich wrote:
> > > Calling XClearWindow() on the TrueColor window should work just fine.
> > > It's not clipped by covering PseudoColor windows and I'm not aware
> > > aware of any bugs in that code. Sounds like you're saying it doesn't
> > > work anymore. If tha
On Fri, 9 Nov 2001, Mark Vojkovich wrote:
>OK. It looks like this there might be a bug in the mioverlay
> code. I'll look into fixing this for 4.2.0.
>
OK, I've fixed this in CVS. Attached is the patch to
xc/programs/Xserver/mi/mioverlay.c.
Mark.
*** miove