× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Progress bars (WAS: performance loading a subfile)
  • From: "James W. Kilgore" <qappdsn@xxxxxxxxxxxxx>
  • Date: Wed, 13 Sep 2000 19:51:51 -0700
  • Organization: Progressive Data Systems, Inc.

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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.