Re: Progress bars (WAS: performance loading a subfile)

I was thinking along the idea of loading every element of the array with 
x'21' and then just clearing them left to right as the xx% increased, with 
fancy foot work around the middle of the bar for the number, or moving the 
number off the bar all together because there was some eye conflict as the 
number moved about on your demo.

Your demo site is nice by the way.
_______________________
Booth Martin
Booth@MartinVT.com
http://www.MartinVT.com
_______________________




"James W. Kilgore" <qappdsn@attglobal.net>
Sent by: owner-rpg400-l@midrange.com
09/13/2000 10:51 PM
Please respond to RPG400-L

 
        To:     RPG400-L@midrange.com
        cc: 
        Subject:        Re: Progress bars (WAS: performance loading a subfile)

Peter,

You're right.  The output is mapped over an array and I put the hex code 
into the
array.

As the hex code meets the xx%, the xx% moves to the right until it can 
jump back
over the hex code to center.

It really is a trivial program, but the users like the estimated time to
completion so they know if they should go off and do something else and 
with the
red bar they can spot from across the room about how much time they have 
left.
I've had jobs that run for over an hour and it drove me crazy wondering if 
the
last change I just made now has me in a loop.

I have found that the time is fairly accurate after it gets to 5%.  Sort 
of like
downloading from the web using Netscape.  The initial estimated time 
starts
dropping like crazy once cache starts loading up and then it settles into 
steady
processing rate.

As I mentioned, the estimated times are totally inaccurate if the file 
being
processed has an OPNQRYF QRYSLT clause.  In some cases where I have two 
files and
am processing with MR, if the primary file has the OPNQRYF, I'll use the
statistics of the secondary file to drive the progress bar.  In other 
cases, if
it was a job run often, I just built a LF and used that in the program.

I wrote it about 8 years ago and ran it through the CVT command so I'm 
sure that
someone can come up with a more "modern" way of accomplishing this.  After 
all,
this is a part of the WyattERP project and is open source! :)

Peter Dow wrote:

> Just a guess, but how about a output-only field 50 characters wide with
> color red, then just place a green attribute byte at the dividing point
> between complete and incomplete based on your % calculation. When it
> changes, you blank out the entire field, put the attribute byte at the
> appropriate positon, and center the xx% done.  Centering the xx% so that 
it
> misses the green attribute byte might be a little tricky, but not
> impossible.
>

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: 
david@midrange.com
+---




+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---