Selection counts are incorrect after invoking some commands with incorrect number of parts selected.

[david-hall]

Selection counts are incorrect after invoking some commands that require a specific number of balls to be selected as their inputs. This only occurs when one or more balls, struts or panels are selected prior to invoking the command, but the selected items are incorrect for the command being invoked, thus generating an error dialog. Once this condition occurs, it will persist as long as the document remains open.

Commands know to cause the problem in version 7.0.64 include:
Select Half Space
Select by Diameter
Select by Radius

All of these are subclasses of the abstract SelectByBoundary class so the problem and/or the solution may be in that common base class.

1. Open a new model.
2. Click on the ball at the origin to select it and note that the measure tab shows 1 ball selected.
3. Select any one of the problematic commands listed above which will generate an error message.
4. Dismiss the error mesage and note that the selected ball count remains unchanged and the ball visually appears selected.
5. Click on the background. This should deselect the ball but instead, it makes no change visually or in the count shown on the measure tab.
6. Click on the ball. This should deselect the ball but instead, it makes no change visually and it increases the count shown on the measure tab to 2.
7. Repeating steps 5 or 6 will now visually cause the ball to alternately toggle between visually selected and deselected. The count will incorrectly toggle between 0 and 2.
8. Repeating steps 2 through 4 will cause the selection count to increase each time the problematic commands are invoked.
9. Drag out a strut while the ball is selected and then click on the strut to select it. This will generate a NullPointerException.

This similar but slightly different problem is probably a manifestation of the same underlying issue.

1. Open a new model.
2. Drag out a new strut and click on it to select it. Note that the measure tab shows 1 strut selected.
3. Select any one of the problematic commands listed above which will generate an error message.
4. Dismiss the error mesage and note that the selected strut count remains unchanged and the strut visually appears selected.
5. Click on the ball at the end of the strut opposite the origin. The ball is selected as expected, but an error dialog shows a NoSuchElementException.
6. After dismissing the error, the measure tab shows 1 strut but no balls selected.

The 'Construct Line-Plane Intersection' command throws an NPE if it is invoked with no strut selected, but it does not seem to impact subsequent selection counts so I'll report it as a separate issue.