Community
Participate
Working Groups
When using the launch configuration route to use the Perfmon, you have to right click on the agent and select "Configure perfmon counters" which opens a little dialog where you pick which counters you want to monitor. The main problem with the dialog is that it's a tree, but you don't navigate it like a normal tree. Normally, you have a [+] where you can expand the tree. This also tells you it's actually a tree. But for this dialog you have to right click on an item and say "Get Children" in order to expand it. It would be much more understandable and usable if you could just click on the [+] and expand it. I understand that expanding means issuing a command that could be slow, but the CVS folks were able to deal with this problem nicely (i.e. expanding all modules under, say, HEAD). The other thing is that usually when we have a list or tree of things to select, where we can select more than one, we use check boxes and check off the ones we want, much like what's currently in the statistical UI with the tree on the left. This bug only applies if we decide to keep this counters dialog. If we have a plan to rework the counters selection (i.e. having them right in the view in the tree) then this one is invalid.
Same as with 73783, this dialog was added as compromise due to failings of the statistical view. The right metaphor here is to use the tree on the left hand side of the view - which is what the editor does. In the current version of the editor you can double click a tree item to get its children or start monitoring it and you can select multiple nodes and choose to get their children or monitor them. The view does not have the extension points necessary for this. The reason why we don't do the expending based on opening the + in the tree is because in order to have the + you need to pre-fetch the children 1 level deep. Straight away this means a lot more bandwidth to get the initial perfmon tree. In addition to this if the user accidentally clicks on the + for the thread node we are going to be fetching thousands of counters which would result in significant delays.
retarget milestone based on Harm's approval on defect re-categorize.
Mark this bug as a duplicate of 73783, and target the feature to be done in 73783 *** This bug has been marked as a duplicate of 73783 ***
This is dup'd to the wrong #
please dup against 78509
*** This bug has been marked as a duplicate of 78509 ***
Closing this duplicate.
