View Full Version : Progress meter VS. StatusDlg

02-05-2004, 07:49 AM

I'm creating an app which will use a Progress Bar to show the status of Zip.Add, a File.Copy and Zip.Extract actions...

I don't know which object to use in my callback functions: StatusDlg or Progress Meter with a Label.SetText() (to inform users about current file and other things).

I will create big zip archives (~ 500Mo, with a lot a small files)

Is one solution more rapid than an other ? Changing the text on a label Object take the same time to change the text of a StatusDlg object ? (I don't want to include current file name on the progress meter object)

Thank you !


02-05-2004, 09:06 AM
Best way to find out is to try them both using a stopwatch. If you can't tell the difference that way, the difference won't matter to the user.

My motto is: design for responsiveness, not speed. Many studies have found that progress displays (whether graphical or text-based) make operations seem to take less time. If a user sees that something is happening, and has something to watch, the whole operation will feel quicker to them, even if it takes longer than it would with no progress.

02-05-2004, 10:42 AM
Good motto Lorne :) I can see the sense in that.

02-05-2004, 01:52 PM
Really, eh? Cool, if you ever have any links to any studies evern remotely in this area of interest please post them, I will read ever single word of every single link. Can never read too many studies on these things.

Corey Milner
Creative Director, Indigo Rose Software (http://www.indigorose.com)

02-05-2004, 02:16 PM
Here's a decent book on the subject:

GUI Bloopers: Don'ts and Do's for Software Developers and Web Designers (http://www.amazon.ca/exec/obidos/ASIN/1558605827/qid%3D1076015397/701-1561223-8964345)