This first combination of options will not work with Bandit/Shadow, as every axis that is moving in Rapid must always be addressed with a "/", thus Gcodes must be nonmodal always.
MODAL COORDINATES AND G CODES
/X-1.4219 /Y-1.1458 /Z0. (Rapid move, correct syntax)
Y1.7396 (considered feedrate move)
X1.6094 (considered feedrate move)
Y-1.1458 (considered feedrate move)
X-1.4219 (considered feedrate move)
G01 X1.6094 Y1.7396 F10.0 (considered feedrate move)
X-1.4219 (considered feedrate move)
This one I can get all right, just as you posted:
NON-MODAL Gcodes and Non-modal Coordinates
/X-1.4219 /Y-1.1458 /Z0.
/X-1.4219 /Y1.7396 /Z0.
/X1.6094 /Y1.7396 /Z0.
/X1.6094 /Y-1.1458 /Z0.
/X-1.4219 /Y-1.1458 /Z0.
G01 X1.6094 Y1.7396 Z0. F10.0
G01 X-1.4219 Y1.7396 Z0.
Here is the third option which I originally spoke of and was having trouble with:
NON-MODAL Gcodes and Modal Coordinates. Notice the "/" that is retained when the associated redundant axis movement is eliminated. Here is what it would turn out like (but is incorrect Bandit/Shadow syntax), using your same code as above:
/X-1.4219 /Y-1.1458 /Z0.
/ /Y1.7396 /
/X1.6094 / /
/ /Y-1.1458 /
/X-1.4219 /Y-1.1458 /
X1.6094 Y1.7396 Z0. F10.0
X-1.4219 Z0.
( I also removed the G01, since this is not required, but this is easily eliminated in the NC setup)
Note, this third permutation of modal options does work correctly in OneCNC Mill Professional.
As I suggested above, the simplest fix would be to allow for unique prefixes to exist in the G00 setup versus the G01 setup for these three:
Value X
Value Y
Value Z
If you can acoomplish this, I think it would be harmless to all other users who are using the standard FANUC-speak.
(and no, I didn't stay up till 4 in the morning to post this
)