Freeze Event Responses...How?
in [Visual Basic]
|
From: Eduardo on 28 Mar 2010 19:24 Webbiz escribi�: >> But... why are the events fired? >> Are you using DoEvents in the procedure that loads the data? > > > I was, allowing for a break. But considering that now I'm disabling > the form for 1 sec, what's the point, right? Who needs to break a 1 > sec load? LOL > > So I've placed the DoEvents before the proc so that the screen can > finish drawing before the proc loop starts. Without DoEvents, the > startup isn't clean as the painting is delayed during data loading and > looks bad. It works good now. But if the user can trigger events in the middle of the load, then you must have DoEvents somewhere in the loop also.
From: Webbiz on 30 Mar 2010 15:23 On Sun, 28 Mar 2010 20:24:35 -0300, Eduardo <mm(a)mm.com> wrote: >Webbiz escribi�: > >>> But... why are the events fired? >>> Are you using DoEvents in the procedure that loads the data? >> >> >> I was, allowing for a break. But considering that now I'm disabling >> the form for 1 sec, what's the point, right? Who needs to break a 1 >> sec load? LOL >> >> So I've placed the DoEvents before the proc so that the screen can >> finish drawing before the proc loop starts. Without DoEvents, the >> startup isn't clean as the painting is delayed during data loading and >> looks bad. It works good now. > >But if the user can trigger events in the middle of the load, then you >must have DoEvents somewhere in the loop also. "I was..." was my reply. :-) Webbiz
From: Eduardo on 30 Mar 2010 22:16
Webbiz escribi�: > On Sun, 28 Mar 2010 20:24:35 -0300, Eduardo <mm(a)mm.com> wrote: > >> Webbiz escribi�: >> >>>> But... why are the events fired? >>>> Are you using DoEvents in the procedure that loads the data? >>> >>> I was, allowing for a break. But considering that now I'm disabling >>> the form for 1 sec, what's the point, right? Who needs to break a 1 >>> sec load? LOL >>> >>> So I've placed the DoEvents before the proc so that the screen can >>> finish drawing before the proc loop starts. Without DoEvents, the >>> startup isn't clean as the painting is delayed during data loading and >>> looks bad. It works good now. >> But if the user can trigger events in the middle of the load, then you >> must have DoEvents somewhere in the loop also. > > "I was..." was my reply. :-) > > Webbiz OK. Then, if you don't have DoEvents in the loop any more, you don't need to disable the form to avoid events either. |