At 01:16 2002-10-10 -0700, you wrote: >All, > > I have implemented my own version of a modal form. I am curious what >exactly 'modal' and 'save behind' actually do in the constructor. Here is >my problem: > >I am opening my own modal form and then I am opening another modal form on >top of it, but, the second form is launched with FrmDoDialog(). When that >form closes, it erases the middle of the form it was opened on top of. I am >wondering if it has something to do with the two mentioned constructor >properties above. > >I use this same FrmDoDialog() call on just about every other form that I >have and I do not see this problem. The only difference that I can come up >with is that I am doing something wrong when implementing my own modal form. > >Any ideas?
Are you seeing this on a device or just under the emulator with debug ROMs. The modal flag tells the system whether it should bring up system dialogs, like the "find dialog". The save behind flag should be set -- it tells the OS that the window will appear above another window, and that the OS should try to save a copy of the screen that was below this window to restore later. Debug ROMs implement aave behind without doing the restore -- instead, they call the form event handlers with frmUpdateEvent messages to get them to redraw. You need to either let this event get to FrmHandleEvent or handle it youself and call FrmDrawForm and do any redrawing when you get it. -- Ben Combee <[EMAIL PROTECTED]> CodeWarrior for Palm OS technical lead Palm OS programming help @ www.palmoswerks.com -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
