On Tue, Sep 05, 2000 at 10:26:35AM -0600, gerard patel wrote:
> At 06:47 PM 9/5/00 +0000, you wrote:
> >have you recently tried winmine; mine comes up in nice a nice 1 bit b&w scheme
> >(hard to tell when it's started, but the gdi lock overhaul may be a good start)
>
> No, nothing to do with the lock in this case; here is the 'fix':
>
> wine:diff -ru init.c.orig init.c
> --- init.c.orig Sat Aug 19 21:41:13 2000
> +++ init.c Wed Sep 6 01:24:31 2000
> @@ -198,7 +198,7 @@
> * a color depth of no more than 8 bits per pixel.For devices with greater
> * color depths, -1 is returned.
> */
> - X11DRV_DevCaps.numColors = (screen_depth>8)?-1:(1<<screen_depth);
> + /* X11DRV_DevCaps.numColors = (screen_depth>8)?-1:(1<<screen_depth); */
>
> /* Resolution will be adjusted during the font init */
>
> My reference 20000801 does not have this feature, so it was added last month it
>seems.
> I feel tired now and I will check MSDN vs reality and try to find who added this
> and why maybe tomorrow :-)
I did. MSDN says it is correct like this, but it could be a GDI32 feature.
> I have a hunch that this could turn out yet another difference 16/32 bits api since
> the MSDN does not cover much of the old win16 api.
winmine.exe does call it and gets back 0xffff (true color).
call GetDeviceCaps
cmp ax, 2
jle ...
...
Apparently 0xffff is less than 2 ... :/
Ciao, Marcus
