David,
Here is some sample code that I use to test the 16-bit color on a Palm. It
is assumed that the device that you are running on is 16-bit color capable.
This code just draws some pretty color bands.:
---begin code---
static void MainUpdateForm(void)
{
int i, j;
PointType topLeft = {0, 16};
RGBColorType RGBColor = {0, 0, 0, 0};
UInt32 depth16 = 16;
WinScreenMode(winScreenModeSet, NULL, NULL, &depth16, NULL);
FrmDrawForm(FrmGetActiveForm());
for(i = 0; i < 144; i++) {
RGBColor.r += 5;
RGBColor.g -= 3;
for(j = 0; j < 160; j++) {
RGBColor.b++;
WinSetForeColorRGB(&RGBColor, NULL);
WinDrawPixel(topLeft.x, topLeft.y);
topLeft.x++;
}
topLeft.x = 0;
topLeft.y++;
}
}
---end code---
Now, when I run it on a real Handspring prism it simply locks up and
sometimes requires a reset. If I run it on the Handspring POSE 3.0a7 and a
non-debug ROM, it simply displays nothing and _sometimes_ I have to reset
but other times I can press some buttons and start some other applications.
I get no POSE errors when I try to do this on the Handspring ROM.
Thanks for your help.
Mike McCollister
> -----Original Message-----
> From: David Fedor [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, December 19, 2000 12:23 PM
> To: Palm Developer Forum
> Subject: Re: WinSetForeColorRGB() Crashes Handspring Prism (Palm OS
> 4.0 header s)
>
> >I have found that I can draw true RGB pixels on the Palm OS 4.0 DR2 ROMs
> >using the WinSetForeColorRGB() and WinPaintPixel() (or WinDrawPixel())
> >functions. But this crashes a Handspring prism.
>
> What function crashes? How does it crash? With an error message? What's
> the
> stack trace? What parameters are you passing? How about posting your
> code?
>
> It does work in general, I know that for sure :-)
>
> -David Fedor
> Palm Developer Support
>
> --
> For information on using the Palm Developer Forums, or to unsubscribe,
> please see http://www.palmos.com/dev/tech/support/forums/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
