Currently, activating a component requires:
(a) Visually identifying which items in the browser are actual components and thus possible targets. This requires visually searching left (irregularly indented) side of the tree.
(b) Hovering the mouse over the component name until the radio button appears.
(c) Moving the mouse the the right side of the item, over the radio button.
(d) Clicking on the radio button
This operation requires far more visual effort and fine motor operations than necessary.
My preference would be not to hide the non-selected radio buttons.
This would visually identify components (more positively than the indistinct and multiple different "component" and "assembly" icons), and give the eye and hand an available visual target to move the mouse towards (instead of requiring hover then jog-to-the-right).
However, I realize that the visual designers may have an insurmountable fetish for suppressing anything perceived by a lay person as visual clutter -- such as the disappearing unselected radio buttons.
So, as a fallback, at least expand the hit region for browser tree items that are components so that it encompasses the area where the radio button will appear. This way, users can move the mouse directly to that location, prompting the button to appear, and then click on it.
This is an ergonomic issue as well as a speed and productivity issue, as it reduces two mouse movements requiring fine positioning each time down to a single move and fine position.
