Community
Participate
Working Groups
UI implementations of IProgressMonitor typically show how many items have been processed so far. This implementation is OK for cases where a build has to compile N files. However, in cases where the operation is going through several main tasks, each having its own subtasks, it is probably better to list all the main tasks in advance, and then draw a checkmark in front of each task text as it has been completed. Progress indicator can still be used to show progress within each of the main tasks. I didn't check IProgressMonitor in detail, but it should be flexible enough to acommodate this implementation without changes. Of course, for this kind of monitor to work, there should not be more than a few main tasks. Otherwise, the indicator will be too tall. NOTES:
Defer
Reopened for investigation
Although I am the originator of this defect, I am not sure I have a scenario to justify it anymore. Clearly, the scenario in mind was related to long operations that have major steps with optional tracking of progress within each step using the progress monitor. Bottom line: we don't have an immediate neeed for this monitor and will not be haeart-broken if you punt on the request.
Punting
