A while back, this post made reference to something I would like to do:
===========================================================
Msg ID: 54709
Subject: RE: Status Bar
Author: William Hanigsberg
Date: 02-13-2002 14:54
File:
Gerard,
"...some of my clients are V-E-R-Y impatient." And I bet they let you know it.
Check out Section 20 of the Xbasic documentation which describes methods for working with the statusbar. They are straightforward.
That said, many users do not look at the statusbar finding it "beneath their notice." I throw up a form and write code which changes the text property of a text object as the process progresses. It is right in the middle of the screen so they cannot miss it.
The final message is "Almost done" so you can see that my users are also impatient!
I can help you with this method should the statusbar not suffice.
Bill
==========================================================
I too, feel that the status bar is easily overlooked and prefer to pop up my own progress bar of sorts. That's easy enough to do when the total length/number of processes is known. One aspect which I have found difficult to quantify is the time a particular query might take. If it is a second or two, there is no need to indicate progress. If it is much longer than 5-10 seconds, it's very informative for the user to know if they can go get a cup of coffee or not. Predicting the length of time a query might take is not straightforward, at least not yet, to me. I can watch for the creation of another $$xxxxx.mpx file, but predicting the name of that file is near impossible.
There are some instances where a user tries to create a query that is overly complex and will require much more time than they would prefer. It would be handy to issue a warning when that situation arises.
Have you, Bill, or anyone else, been able to deal with this issue effectively?
Tom Lyon
===========================================================
Msg ID: 54709
Subject: RE: Status Bar
Author: William Hanigsberg
Date: 02-13-2002 14:54
File:
Gerard,
"...some of my clients are V-E-R-Y impatient." And I bet they let you know it.
Check out Section 20 of the Xbasic documentation which describes methods for working with the statusbar. They are straightforward.
That said, many users do not look at the statusbar finding it "beneath their notice." I throw up a form and write code which changes the text property of a text object as the process progresses. It is right in the middle of the screen so they cannot miss it.
The final message is "Almost done" so you can see that my users are also impatient!
I can help you with this method should the statusbar not suffice.
Bill
==========================================================
I too, feel that the status bar is easily overlooked and prefer to pop up my own progress bar of sorts. That's easy enough to do when the total length/number of processes is known. One aspect which I have found difficult to quantify is the time a particular query might take. If it is a second or two, there is no need to indicate progress. If it is much longer than 5-10 seconds, it's very informative for the user to know if they can go get a cup of coffee or not. Predicting the length of time a query might take is not straightforward, at least not yet, to me. I can watch for the creation of another $$xxxxx.mpx file, but predicting the name of that file is near impossible.
There are some instances where a user tries to create a query that is overly complex and will require much more time than they would prefer. It would be handy to issue a warning when that situation arises.
Have you, Bill, or anyone else, been able to deal with this issue effectively?
Tom Lyon
Comment