It has been implied to me that this is possible, setting up an offscreen window in storage RAM when dynamic RAM is full, using FtrPtrNew()...and that while you can't blit TO it (must DmWrite, I suppose), you CAN blit from it (making it handy for the ever-popular WinCopyRectangle)...
I'm wondering what approach one would take to set an offscreen window up in this manner? Should I create an offscreen window in RAM, ask for feature space of the same size, MemMove a copy of it, then deallocate the original...no, that seems insane. Would I just allocate (FtrPtrNew) the window structure first, empty, then allocate the bitmap manually and set the window pointer up manually?...Or perhaps only have the bitmap in feature memory and the window structure in dynamic RAM?...Or allocate it all at once?... Very little feature experience (and none doing this), and I've always just asked for an offscreen window from the usual WinCreateOffscreenWindow(), so I don't know much about the inner workings of windows, but it would be very nice to figure out the "right" way to do this. Suggestions?...Recommended reading? I've pored over feature functions a bit, but the best way to do this for an offscreen window is not yet obvious to me. Thanks in advance, zane ----- r. zane rutledge - http://www.rzanerutledge.com/palm/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
