On Thu, 13 Jun 2002, David Fedor wrote: > So unless you're willing to implement a lot of special cases and don't mind > doing frequent software updates, it is far safer to directly twiddle the > bits in an offscreen window, and then copy that offscreen window to the > screen with WinCopyRectangle et al. The blitter will convert it as > necessary.
it has been mentioned many times that if you want to do direct access, you can do so on your offscreen windows/sprites whatever, but, for compatibility purposes you should not have a custom blitter from offscreen to the real screen - unless you are sure about what you are running on. a WinCopyRectangle() from offscreen -> real screen will handle all "issues" regarding endianess et al. at least, on most devices :) the only case where this doesn't work was on the Handera units. they decided to be "over smart" and when you allocated a window of 160x160, they allocated memory for 240x240 - so, your memory layout was not what you expected so direct banging = bad the workaround on these units was to create a bitmap first, then a window from that bitmap. using WinCreateOffscreenWindow would actually scale your width,height by 150%. // az [EMAIL PROTECTED] http://www.ardiri.com/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
