Timer does not respond at set intervals

[NasibKalsi]

Hello All:

I wonder, if possible that the timer will update during indexing.

Full Story:
I am indexing many large files.
I created another form with the timer on it. I run this form just before the indexing. The timer is not responding at intervals(500), but between index files.

Is this a normal behavior or I am missing something ?

my best

 

[Mike Lewis]

My understanding has always been that the timer doesn't fire while a command is in progress. It only fires between commands and when the application is "at rest" (e.g. at READ EVENTS).

If the interval expires while a command is in progress, the timer will still fire, but it will wait until the command finishes.

As I say, that's what I've always understood. Perhaps someone could correct me if I'm wrong.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro tips, advice, training, consultancy
Custom software for your business

 

[DSummZZZ]

That sounds about right Mike.

On another note though, if a form is running in a separate process than what called the indexing commands, it could be that the indexing process is hogging all the processor time.

If you're trying to somehow perform user notification of indexing status or something like that, you're most likely out of luck.


-Dave Summers-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm

 

[NasibKalsi]

Thank you Mike and Dave.

I just was not sure about its behaviour.

If I create RAM resident program to replace the timer event, and pass progress message as required. That is I have 2 process master and the child(messenger). Any suggestions ?

 

[Mike Lewis]

NasibKalsi,

I'm not sure what a "RAM-resident program" is. It sounds difficult, but if you are happy you can do it, that's fine.

What I usually do in this situation is to display an animited GIF while the process is in progress. The GIF might be a rotating circle or a moving "barber pole" or anything else that conveys the idea of motion. Obviously, it's not a true progress bar: it doesn't tell the user how long they have to wait or whether the program has crashed, but it does give a measure of reassurance.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro tips, advice, training, consultancy
Custom software for your business

 

[NasibKalsi]

Thanks Mike

Gif was another thing I was thinking to do.

I just remember that now, it is TSR (Terminate and Stay Resident". It was very popular in the 80's(Side kick, etc).

My Best

Nasib

 

[Mike Lewis]

Nasib,

Yes, I remember TSRs and Sidekick. I even wrote a few myself. But they belong in the DOS world. I can't imagine that they have an equivalent in Windows - except maybe tht all programs are now memory-resident.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro tips, advice, training, consultancy
Custom software for your business

 

[craigber]

Any running program in Windows is considered "RAM resident"

Craig Berntson
MCSD, Visual FoxPro MVP,

http://www.craigberntson.com/blog