Thanks for your answer, this is actually what I was doing but it didn't work your e-mail made me look more carefully about it and it appears that the screen erazure occurs BEFORE the call to winscreenlock. Using the debugger I found that the blanking occurs in frmCloseEvent handling in FrmDispatchEvent and therefore before I could lock the screen in frmOpenEvent handling.
Best regards Benoit Cerrina "P & C Soldan" <[EMAIL PROTECTED]> a �crit dans le message de news: [EMAIL PROTECTED] > What was the user looking at before the winscreenlock command? If you were > showing them something then simply using the winlockcopy option will solve > the problem. Otherwise you may consider showing them something first and > then winscreenlock(winlockcopy). > > peter > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
