It could be the keyboard plugin if ya consider that being seperate but I still consider that part of the Mach4 software.
I agree on both counts. A plug-in provided by Newfangled Solutions is definitely a part of the software.
This bug got my attention because I am finishing up a jogging device at this time. I started MACH4 with a continuous stream of jogging moves flowing into MACH4 from the TCP Modbus to the PLC script (ahead of all the enabling code) and there was no movement and nothing was queued up or buffered from the input stream.
Keyboards and/or their associated drivers (be it MACH4, Windows, various key grabbers, key snoopers and so on) have buffers, so I would speculate that the problem is in the plug-in. I'm guessing that the user does not have access to flush the buffer on startup and it would *appear* that MACH4 and/or the Plug-in is not doing that either. That would explain keystrokes being stored and released to MACH4 as soon as it accesses the plug-in.
I'm not a keyboard expert by any means, but I would not be surprised to find that the physical keyboard itself has a small internal buffer, in which case, flushing the Plug-in may not be adequate. The plug-in would need to collect all available characters in the keyboard buffer and flush everything before passing the first post-initialization key code.
The above is purely speculation on my part, and even if it is correct, I don't think the user has access to the area where a solution can be made. Very nasty bug. Hopefully this one gets escalated.