At 4:31 PM +0100 1/19/00, Bob Ebert wrote:
>At 9:00 AM +0100 19-01-00, Brian Hall wrote:
>>Turns out I had a chore that waited until FrmGetFormID(FrmGetActiveForm())
>>was the status form it had created, and then created the connection (which
>>in the case of a net connection, caused the dialing status dialog to pop
>>up). However, it turns out that this was *before* the form could get drawn
>>by the open handler for the status form. I added a call to FrmDrawForm and
>>the problem went away. Not sure if this is the 'right' way to solve it, but
>>it did work.
>
>Ah, right, so I'll add caveat 3:
>
>3) Don't assume that because your form is active it has been drawn.
>
>I think your solution will work. Another way to solve the problem would be
>to test FrmVisible and wait until your form is both active AND visible.
Since that was more in line with my original logic, I gave that a try and
it worked fine. The new test is:
if (FrmGetActiveFormID() == sendStatusForm &&
FrmVisible(FrmGetFormPtr(sendStatusForm))) {
// move to next state, which opens the connection
}
Might be handy to have that in the KB!
Brian
_____________________________________________________________________
Mark/Space Softworks voice 408-293-7299
111 West Saint John, 3rd Floor fax 408-293-7298
San Jose, CA 95113 <http://www.markspace.com>
PalmOS, Mac OS, Windows and Web Software & Solutions:
PageNOW! Wireless Messaging, PhoneWatcher Caller ID,
Online & Communicate terminal emulation and serial debugging
