In responding to Bernard's request to leave the status bar up after the "OK' button has been pressed, I noticed the various error handling.
I'd like to indicate an error by drawing the rest of the bar in red, so a failed condition would be shown by a bar that was green to the point of failure, and then red after. If you noticed, the bar is now marked into 5% blocks, so you could look at the bar and get some estimate of the percent completed before failure. +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ |GG|GG|GG|GG|GG|GG|GG|GR|RR|RR|RR|RR|RR|RR|RR|RR|RR|RR|RR|RR| +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ So, in the above ugly ascii graphic, where "G" is green and "R" is red, a failure at about 38% is indicated. Clearly, there's no definition of what 38% actually means, nor am I suggesting any such documentation. Do you think that would be evident to someone looking at the bar? That is, could I reasonably expect people to interpret an all-green bar as a successful completion and a part-green, part-red bar as failed? Furthermore, be able to see approximately where the build failed? Don't forget, they would have also sen an appropriate message explaining the failure. Alternatively, is this getting too goofy, and I should just quit mucking about... -- David N. Lombard Rossmoor, Orange County, CA N 33 deg, 48', W 118 deg, 5' ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Oscar-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-devel
