Thank you, this worked fine. Neither the mentioned drawback nor the fact that it is not available before 3.5 is a problem as like mentioned by Ben this is largely cosmetic.
Is there some performance advantage to this method compared to the one described in my previous mail. I am wondering about changing the other places where I use double buffering to using this instead. Benoit "Ben Combee" <[EMAIL PROTECTED]> a �crit dans le message de news: [EMAIL PROTECTED] > At 10:59 AM 9/20/2004, you wrote: >>As far as I can tell, it's impossible to have FrmDrawForm output to >>anything >>other than the screen window, even if it is not the draw window. However, >>there are methods of avoiding flicker. What exactly is causing the >>problem? >> >>If it's custom drawing, you can do that offscreen before the form is >>displayed, then draw the form, then copy it onto the form. The window >>copy >>function is sufficiently fast for this. > > WinScreenLock and WinScreenUnlock were introduced to the OS to handle > "flicker-prevention". You lock the screen before a big update, do all > your form manipulation, then unlock it. These APIs may not work if > there's insufficient memory, but their use is cosmetic anyway. > > > -- Ben Combee, Technical Lead, Developer Services, PalmSource, Inc. > "Combee on Palm OS" weblog: http://palmos.combee.net/ > Developer Fourm Archives: http://news.palmos.com/read/all_forums/ > > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
