There were several bugs with the same root cause in the Multi-Axis Jog Screen related to the touch screen or mouse processing of the jog buttons.

1. Clicking on the jog button and dragging the mouse out of the button area left the Axis jogging.

2. Dragging the mouse from outside of the button to inside of the button and then releasing could cause an Axis not Enabled error when technically the button had not been clicked nor had any attempt to jog the axis been made.

3. Selecting the Yes button in the Reference, Are You Sure window could sometimes erroneously result in the Axis not Enabled error window being displayed.

The root cause of these problems was a bug in how the jog buttons generated the PSF_RELEASE signals. The problem was actually in all buttons but the jog buttons are the only buttons that use these special signals created specifically for jogging.

For problem 1 the PSF_RELEASE signal was not being sent when it should have been. Problems 2 and 3 were caused because the mouse was released over the button and the PSF_RELEASED was being generated even though the button had never actually been pressed. For problem 3 the when the mouse was released the pointer was within the area of the Jog Button and it generated a PSF_RELEASED signal that it should not have.

These issues have been fixed.