2010/9/17 Juha Manninen (gmail) <[email protected]>: > I committed it in r.27384. > Now I call AddOnIdleHandler before creating the form. I also tried passing > variables through form constructor and calling AddOnIdleHandler from > Form.OnCreate handler, like CodeBrowser does. It made no difference so I > didn't > commit it. I think CodeBrowser's secret is splitting the task and using a > sequence state flag.
Yes, I think so too. > > I think my solution is good enough now because the delay is typically short. > Earlier there was no visual feedback, now there is a grey form at least. > If you have only one step, I see no use for the OnIdle Handler, there are probably better events then, that fire when the form is shown or after it has been shown to the user. Vincent -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
