прогресс бар ie

Is the task continuous? If the task never completes, there’s no need to show its progress. Examples of continuous tasks include antivirus scans and file indexing.

In the incorrect examples, the taskbar button progress bars aren’t very useful.

Is the progress feedback useful and relevant while using other programs? That is, are users likely to monitor the progress while using other programs, and change their behavior as a result? Such useful and relevant status is usually displayed using a modeless progress dialog box or a dedicated progress page, but not with a busy pointer, activity indicator, or progress bar on a status bar. If the status isn’t useful when using other programs, just display the progress feedback directly in the program itself.

Like any new shiny piece of technology everyone wants to add it to their program. The flip side is that most of the times you shouldnРІР‚в„ўt use it. Let me quote the directly:

Of course, what good is integrating this shiny new behavior into your apps if isn’t backward compatible with Windows 2000, XP and Vista? None at all. And since this taskbar behavior is included in wyUpdate & wyBuild 2.2+, backwards compatibility is a must. Here’s our running on Windows 2000 – Windows 7:

The first control I want to give you is a way to use the new progress bar in your appРІР‚в„ўs taskbar icon. This is what the new taskbar progress bar looks like when Internet Explorer downloads a file:

Windows 7 will be available for download to MSDN and Technet subscriber in less than 2 weeks. I thought IРІР‚в„ўd introduce a few controls to make Windows 7 development easier for C# and .NET programmers. The controls will be written for .NET 2.0 & Windows Forms, but will obviously be compatible with .NET 2.0, 3.0, 3.5 and the upcoming 4.0.

Wyatt Says... is a collection of design articles by Wyatt O'Day. I want to help you make your programs great and your users happy.**Or as we say in New England, "wicked friggin' happy"