Post by Stefan on Oct 15, 2022 2:23:43 GMT -5
George,
Not sure how easy this is.
The MK and CK macros are actually the exact same code. The MOVE/COPY action path is triggerd (in part) by the first character of the macro name.
Hence I figured that a simple SET.ALIAS.MK = CK statement would avoid the need for two spearate macros.
And for the invocation as a primary command, it does indeed work brilliantly.
But the MK and CK commands can also be used directly as LINE commands. In this case, the ALIS assignment does not apply, so MK/MKK is an unknown command.
My Suggestion hence is: Could a SET ALIAS.xx = yy entry also be applied to lien commands?
No drame if not. For the time being, I simply #INCLUDE CK.MACRO within MK.MACRO, so there's only one code deck to maintain, but of course there's still a need for two macros in the library.
