When going through the initial steps of a job, Carbide Motiion will raise a dialog asking for the next bit. I have had several occasions when if I anticipated its next question, and clicked that button as soon as it appeared, I could get CM stuck to the point where I would need to power-cycle the controller and quit and restart CM.
What I have had to do is train myself to wait until the main window’s Start button (in the background, below the sub-dialog asking for the tool) changes from “slightly paler yellow” to “dark yellow”, no matter if the sub-dialog’s Okay button is ready to take a click or not. If I wait and do that, then the tool measurement cycle works correctly.
There’s two different things that I want to point out about this: first, if a button is visible and not disabled, it should accept a click. If it can’t pass that click along, it should schedule it so it will succeed later, when the receiver can accept it.
Second, the visual difference between an active and disabled button should be much more than a slight shade of yellow. Yellow is a very difficult color to differentiate in value, even for people with perfect color perception.
The whole custom color button scheme in Carbide Motion is something that grates on me quite a lot, since doing nothing (using the stock buttons provided by the OS) would leverage the years decades of effort that has gone into making those buttons accessible by people with all levels of vision. And then, if that underlying button was actually disabled, you’d be able to tell the difference even if the main window wasn’t focused.