I'm having trouble communicating, because it seems everyone focused on the absolute technical accuracy of my original response. I was trying only to give a contextually accurate response for your specific question.
Both Ben Combee and I answered your original question. You can't do it on OS 3.0 through OS 3.3 because the OS is hard coded to use black and white. The APIs for controlling the UI object colors are only available on OS 3.5 and higher. (Hopefully this time my answer is both contextually correct and 100% technically accurate ;-). Ok, I can already see a way that my answer is not technically accurate. Sure you can do it on OS 3.0 through OS 3.3 -- for example, you could create your own code to replace the OS code for the UI objects. The point is, there is no built in way to do what you want on OS 3.0 through OS 3.3. If you feel it's important to do on those OS versions, then you need to do it yourself from scratch (or find someone else's code that has already done it all from scratch -- I don't know of anyone who has done so, and it seems like quite a bit of work for very little benefit, so personally I would never bother, even if a paying customer thought it was extremely important ;-). "g3BEPA" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > There is still something that is not very clear. Yes, I want to use > gray colors in versions between 3.0 and 3.5, yes I can legaly set 2- > bit depth, yes I set fore and back colors with WinSetColors, yes I > write directly to screen memory to do some of the operations, BUT : > when I use WinSetColor and change the fore and back colors the > controls I draw after that are using new colors - that's ok. The > problem is that when you move the scrollbar for example it messes up. > In OS 3,5 you can see in the OS code that they use > UIColorSetTableEntry, every time a scroll bar is being drawn, to set > its colors. If you use UIColorSetTableEntry to change the proper UI > colors the scroll doesn't mess up. So in OS 3,5 draw routine uses UI > color list to draw the scroll bar. The question is : what is scroll > draw func using in OS prior to 3,5 (and bigger than 3,0). > > --- In [EMAIL PROTECTED], "Aaron Ardiri" <[EMAIL PROTECTED]> > wrote: > > > >We said the same thing. :-) > > > >The OS 3.0 does not support grayscale -- no built in API support. > > > > > > 3.0 supports grayscale screen at the Win API level, but not for > user > > > interface UI objects or drawing. Actually, the pre-3.5 API was > called > > > ScrDisplayMode, and got renamed to WinScreenMode with that OS > version. > > > > > > >The 3.0 devices have hardware support for grayscale, and you can > force > > them > > > >to do grayscale if you use special techniques. > > > > > > Special techniques == writing directly to screen memory. :) > > > > you could always write directly to the screen. 3.0 API's actually > had > > support for grayscale (ie: WinDrawBitmap etc). so, the only time you > > had 'special' code was pre 3.0, and, thats when you had to tweak the > > CPU into grayscale (CPU had display controller onboard), and, since > you > > were tweaking, you had to write your own drawing routines, as, the > > API's were specifically ONLY 1bpp pre 3.0 > > > > i am 100% sure of this :) i wrote games for 2.0 :P > > > > --- > > Aaron Ardiri [EMAIL PROTECTED] > > CEO - CTO +46 70 656 > 1143 > > Mobile Wizardry > http://www.mobilewizardry.com/ > > > > > > -- > > For information on using the Palm Developer Forums, or to > unsubscribe, please see http://www.palmos.com/dev/support/forums/ > > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
