| Summary: | [TCF][Process] Process monitor refresh settings misses options | ||
|---|---|---|---|
| Product: | [Tools] TCF | Reporter: | Uwe Stieber <uwe.st> |
| Component: | Target | Assignee: | William Chen <william.chen> |
| Status: | CLOSED DUPLICATE | QA Contact: | Uwe Stieber <uwe.st> |
| Severity: | normal | ||
| Priority: | P3 | CC: | cdtdoug, martin.gutschelhofer |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Uwe Stieber
Hi Uwe, Process Monitor has a "start" and "stop" tool bar button which can be used to start or stop auto refresh. There's a "refresh" tool bar button too, which can trigger a manual refresh when the auto refresh is stopped. Of course you can start a manual refresh too even if it is refreshing automatically. Another tool bar button can bring up a dialog, where the user can define a customized refreshing interval as he wants. This tool bar button also has a drop-down menu, where a group pre-defined grades of refreshing speed can be selected. It has a group of menu items to remember a MRU(most recently used) list. This pre-defined refreshing grades can be changed in the preference page too. Can't that satisfy the "Off"/"Custom" needs? -William There should be no "start"/"stop" at all. Haven't see those buttons yet. The auto-refresh starts/stops automatically depending on the selected refresh rate. All the user shall have to do is to set the refresh rate. "Off" typically represent the refresh rate of "0 sec". - The "start"/"stop" buttons should go away. - Do not add another button for "custom" please - "Off" and "Custom" should be added to the button with the drop down menu. "Off" on the top (first item) and "custom" on the bottom (last item). Focus on performing operations with as less clicks as possible with a minimum set of controls. You can experiment with a slider widget in the toolbar too if you like. The button with the drop-down menu should be really enough to configure the auto-refresh. *** This bug has been marked as a duplicate of bug 368321 *** |