>As long as you create your offscreen window using nativeFormat, it >should work fine. I do this in my app and it renders correctly on both >the m130 (OS 4.1) and my Tungsten T (OS 5.0). > >So, the call should look like: > > Uint16 err; > WinCreateOffscreenWindow(160, 160, nativeFormat, &err);
So, when I draw to the offscreen window, I then set the Screen density? For example, if I call WinDrawLine() to draw to this native window, do I have to convert the coordinates by doubling them? Or, do I simply call the API to set the screen coordinates to double? >Even though you specify 160x160, by using nativeFormat, it'll actually >create a 320x320 surface on double-density devices. If you're doing >double-buffering using an offscreen surface, you should be using >nativeFormat anyway, since that will copy to the display the fastest. I'm not double-buffering. I just draw the entire graph off-screen and then copy it on-screen once I have finished the drawing. >By the way, if you read the Palm OS Companion/Reference docs, available >at PalmSource, it would tell you all this. Actually, it doesn't. I mean, I read both of those, and it explained very little. It presumes you already know about how drawing stuff works in general...and I don't. I've not done much in the area of graphics before, so it is all new. I have scoured the reference manual, but still don't understand how it all comes together. The Companion doesn't offer much information at all. Ryan - Eron -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
