|
Ok, my last question(s) on the subject. Making an attractive progress bar on the bottom of green-screen is very simple. (Anyone that wants a .gif of one just e-mail and I'll return a gif for you to look at). The only variables in the Progress Bar are: Starting time, Total Records, Records counted so far, records chosen so far, and Time now. There is a couple lines of code to establish the Percent Counted So Far and also to estimate the time remaining. Then there is a couple more lines to concatenate a string to be presented in the Progress Bar screen format. My question(s) have to do with making this into a prototype. For a prototype: StartingTime and TimeNow are not Parms. TotalRecords is a parm(but needed only once?) and then RecordsCountedSoFar and RecordsChosenSoFar are the only two parms that change as the process runs. As a last step in the cycle one does a WRITE PrgBarFmt to display the Progress Bar. If I understand what all of you are saying then any program could have PR D-specs for the Progress Bar and one line of code inside a record-reading-processing loop that would be: C Call ProgressBarPR(TotalRecords:RecordsCountedSoFar:RecordsChosenSoFar:MsgFlag) My questions: 1 - Is this a reasonable usage of the Prototype? 2 - what are the implications for performance? Will this hurt performance as compared to doing the same process within the calling program? _______________________ Booth Martin Booth@MartinVT.com http://www.MartinVT.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 +---
As an Amazon Associate we earn from qualifying purchases.
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.