Thought I'd move this over to plucker-dev On Fri, Aug 15, 2003 at 10:38:49PM +0200, Michael Nordstrom wrote: > On Fri, Aug 15, 2003, Michael Nordstrom wrote: > > > However, it seems like some 3.5 devices can display 16bpp... > > I've changed the code in the main trunk to first ask the device about > its supported bit depth and then, if necessary, adjust that setting > for the specific OS version.
I'm a little confused on your reasoning behind this. WinScreenMode( winScreenModeGetSupportedDepths, ... ) will only query the device for what it can physically display, not for what the OS can actually display. I know that later on you adjust the maxBitDepth to what it should be given the actual OS itself, but I have a couple comments... 1. I dont think that this will do anything to help solve the original problem pointed out by Stefan Dannemann in http://lists.rubberchicken.org/pipermail/plucker-list/2003-August/003091.html 2. What exactly is the point of using WinScreenMode() to get maxBitDepth if you're only going to prop up the results later on. -- Adam McDaniel Array.org Calgary, AB, Canada _______________________________________________ plucker-list mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
