D
David D Webb
Ok, really just venting here, but why did they change it so the form doesn't
display until AFTER the Load event processes in CF2.0? So if you have any
amount of processing in the load event, nothing is showing until the
processing is complete. I used to be able to show a blank form with a wait
cursor - which worked well because the user knew "something" was happening.
Now I have to put a timer on every page and process it from there.
Worse yet, if you throw up a dialog box that just displays a status while a
process runs, then exits, that form will never show.
You also can't do a form.Show() from the load event of another form. You
have to use form.ShowDialog() (thanks Ginny) which means the underlying form
doesn't continue to load until the top form closes.
Anyway, if you are planning on converting to 2.0, be warned the form display
logic has changed. Timers will get around most problems.
-Dave
display until AFTER the Load event processes in CF2.0? So if you have any
amount of processing in the load event, nothing is showing until the
processing is complete. I used to be able to show a blank form with a wait
cursor - which worked well because the user knew "something" was happening.
Now I have to put a timer on every page and process it from there.
Worse yet, if you throw up a dialog box that just displays a status while a
process runs, then exits, that form will never show.
You also can't do a form.Show() from the load event of another form. You
have to use form.ShowDialog() (thanks Ginny) which means the underlying form
doesn't continue to load until the top form closes.
Anyway, if you are planning on converting to 2.0, be warned the form display
logic has changed. Timers will get around most problems.
-Dave