ESCape key issues in Pre1-4587 build ???

Since the new build got installed.. the ESCape key doesn't seem to function correctly.

If in the middle of a job, you hit the ESC key to terminate it, for a problem ( And boy, do I have problems... ) The system stops immediately. Great! BUT... the manual keys are disabled.. you cannot move the Z axis up or down with the PgUp or PgDn keys, and you cannot move the X or Y axis using the arrow keys.

In order to restore operation, I had to exit LinuxCNC, then reload it. Once I did that, and then hit the X button and enabled the machine.. I can then use the arrow keys. This did not appear to be an issue in previous builds.. but to be honest, it has been one or two builds ago that I last used the esc to prevent my bit from killing itself.

What screen are you using?

Chris

?? Axis Screen ?? You may need to be more specific to How to Tell you what screen I am using. Please remember that some of us just like to install and use the software. I have an RS485 controlled spindle, two parallel ports. Problem seems to happen when the machine is driving spindle and going into piece.

He was asking which user interface are you using, Axis, Gmoccapy. ..

Axis ..

Is it just that the MDI tab rather than manual tab is active?
Manual jog keys only work with the manual tab showing.

No, the MDI tab was not active. I was in the middle of a run, so I had pressed the R key to run the program.. after that, I do not touch the interface again till the job stops. I have been using LinuxCNC for a few years now, and it's possible I could have made a rookie mistake like that ... but no, it was not in the MDI tab mode.
It was either going into the wood or close to that when I hit the ESC key, stopping the spindle and motion. When I tried to use the PG UP key, nothing happened. None of the other keys worked until I rebooted.

Are you using parallel port ?
That behaviour is indicative of interference to the parallel port, you should check the grounding and shielding.

shipmodeller wrote: No, the MDI tab was not active. I was in the middle of a run, so I had pressed the R key to run the program.. after that, I do not touch the interface again till the job stops..

Another possibility is if you have a GladeVCP tab open. If the mouse cursor is over the GladeVCP then that grabs the keyboard events.
This used to drive me mad on my old Axis lathe, but an MPG works better than the keyboard in every way and is a complete fix

I've noticed If you click off the window, like the desktop it won't respond to keyboard shortcuts either