At 1:37 AM -0500 11/18/02, Matt Disher wrote:
In one of our apps, we do the following:

<snip>

This works well, actually, on all 3.5/4.x devices and to-date have experience no ill effects. However in OS/5 the Simulator blows up big time at the MemPtrSize() function. If there's a better way to get the size of the bitmap, I'm open to it.
I'm curious...why do you need to know this? Could it be that the answer is "don't do that"?

On a side note, has anyone published anything that discusses how programs that scribble on the screen can capture the screen or portions from in PalmOS 5 and what we'll need to do to make that compatible with earlier versions? And backwards?
Well, the answer to that is definitely "don't do that". That is, don't try to copy *from* the screen. Instead, draw to an offscreen buffer and copy that *to* the screen.

-- Keith Rollin
-- Palm OS Emulator engineer

--
For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/


Reply via email to