I confirm, the same problem. It happens exactly when the key is released and gscreen calls
Code:
self.gscreen.do_key_jog(_X, direction, False)
Thus it calls jog while the other is still in progress. If the movement is incremental and the key is not released until the movement is complete, then there is no error. In the source code it looks like this:
Code:
int emcTaskSetMode(EMC_TASK_MODE mode)
{
int retval = 0;
if (jogging_is_active()) {
emcOperatorError("Ignoring task mode change while jogging");
return 0;
}
...
I thought the problem was with my custom panel implementation, but the standard one has the same problem. Any ideas on how to fix this?