Hi,
to be honest I think you are going about this the wrong way.
I still find myself hitting <Enter> occasionally after typing an MDI, a hang over from Mach3 days but I don't find using the
<MDI Cycle Start> button that onerous....but perhaps you do. What you are trying to do here is 'fix a perceived
problem that is in fact no problem at all, just a new, Mach4, way of doing things'.
Given that proviso......then you can use the keyboard plugin to capture any <Enter> keypress. If you so desire
you can cause such a keypress to issue an MDI Cycle Start.
I forsee a problem that there are a number of circumstances that you would use <Enter> keypress, not all of them
associated with MDI, are you sure you want to issue an MDI Cycle Start at EVERY <Enter> keypress?
Of course using the keyboard plugin as I am proposing you could choose other than Enter as a keypress to start an MDI command,
maybe the <Space Bar> for instance. That might reduce the number of occasions that you accidentally start an MDI command.
There is a video by Daz-the-Gaz about using the keyboard plugin.
https://www.machsupport.com/forum/index.php?topic=31585.msg219180#msg219180The upshot is that the keyboard plugin can launch a number of 'Mach Actions' in response to a defined keypress....but what happens
if one of Machs stock actions is not what you want. That is what Daz's video is about.
You can cause the keyboard plugin to trigger a Mach signal, mc.ISIG_INPUT33, for example. Now every time you press the <Space Bar>
Input #33 would trigger. Now you just have to put Input #33 into the SigLib{} table as you would with any other input signal
and cause the appropriate action. If you are not familiar with the SigLib{} table......you are in for a treat!! It is a very VERY
VERYclever way to deal with signals, both input and output, that is new to Mach4 and not even dreamt about in Mach3. Look at my .pdf on it:
https://www.machsupport.com/forum/index.php?topic=40051.msg267764#msg267764Craig