Does anyone know of a better method than fastDoEvents() to get the DOEVENTS
command to process correctly? I am running with VFP 8 and even with using
the FORCE option I am still having problems when embedding the webbrowser
control onto forms. Essentially the system will do nothing until I move the
mouse around which I think forces the events to fire.

Re: doEvents by Jack

Jack
Sun Jun 04 11:32:57 CDT 2006

I have also had situations in which even with the FORCE options events
did not seem to be processed. I was able to 'fix' it by setting up a
timer (whose Timer method did nothing) with a relatively short
interval (about 100 msec).

On Sun, 4 Jun 2006 22:19:36 +1000, "Paul Hemans"
<pauln.o.s.p.a.m@laberg.com.au> wrote:

>Does anyone know of a better method than fastDoEvents() to get the DOEVENTS
>command to process correctly? I am running with VFP 8 and even with using
>the FORCE option I am still having problems when embedding the webbrowser
>control onto forms. Essentially the system will do nothing until I move the
>mouse around which I think forces the events to fire.
>

Re: doEvents by Thomas

Thomas
Sun Jun 04 13:40:27 CDT 2006

Jack Jackson schrieb:
> I have also had situations in which even with the FORCE options events
> did not seem to be processed. I was able to 'fix' it by setting up a
> timer (whose Timer method did nothing) with a relatively short
> interval (about 100 msec).
>
> On Sun, 4 Jun 2006 22:19:36 +1000, "Paul Hemans"
> <pauln.o.s.p.a.m@laberg.com.au> wrote:
>
>
>>Does anyone know of a better method than fastDoEvents() to get the DOEVENTS
>>command to process correctly? I am running with VFP 8 and even with using
>>the FORCE option I am still having problems when embedding the webbrowser
>>control onto forms. Essentially the system will do nothing until I move the
>>mouse around which I think forces the events to fire.
>>
In some situations (often involving activeX controls) even a combination
of timer events, programmatic mouse moves and doevents left the cpu
hanging in a specific method. We bracketed the "typical" lines with
"please move the mouse if you can read this" in a nowait-wait window
and cleared the wait wind directly afterwards. Most of the time the WW
was not seen, and if the machine hung, the instruction was already on
screen <g>.

not sweet smelling code, but better than calls to the hotline <g>

my 0.02 EUR

thomas

Re: doEvents by Paul

Paul
Tue Jun 06 13:47:21 CDT 2006

Well, yes, a little unusual but if all else fails .... it works.
Seems a pity that they haven't resolved this yet.



Re: doEvents by Dan

Dan
Wed Jun 07 11:05:02 CDT 2006

It might not be a VFP issue. <s> If an ActiveX control leaves the
environment in a state that VFP isn't expecting, there's not a lot that can
be fixed from the VFP side. <shrug>

Dan

Paul Hemans wrote:
> Well, yes, a little unusual but if all else fails .... it works.
> Seems a pity that they haven't resolved this yet.