01-19-2021, 07:53 AM
Hi Thomas,
I've thought a bit and the requirement to stay within the existing command framework kind of defies "proper" interface design, but here I go:
As suggested by you PRF1/2/3/4 shall be used to provide an additional parameter.
BRK 2xx jumps n times to row/position xx in the same pattern (forward and backwards). n is provided by PRFx. I don't know wether allowing for more than 100 rounds is required (read: I think 100 repetitions is enough).
BRK 3xx/4xx/5xx/6xx conditionally jumps to row/position xx in the same pattern (forward and backwards). The condition is TRUE when CV In 1/2/3/4 is "high" (I don't think that comparing CV In 1/2/3/4 against a specific value provided by PRFx would be more useful - others may differ).
I'm not convinced the above provides for a clean interface, but w/o adding new mnemonics that seems to be the best I could come up with.
Kind regards,
Michael
I've thought a bit and the requirement to stay within the existing command framework kind of defies "proper" interface design, but here I go:
As suggested by you PRF1/2/3/4 shall be used to provide an additional parameter.
BRK 2xx jumps n times to row/position xx in the same pattern (forward and backwards). n is provided by PRFx. I don't know wether allowing for more than 100 rounds is required (read: I think 100 repetitions is enough).
BRK 3xx/4xx/5xx/6xx conditionally jumps to row/position xx in the same pattern (forward and backwards). The condition is TRUE when CV In 1/2/3/4 is "high" (I don't think that comparing CV In 1/2/3/4 against a specific value provided by PRFx would be more useful - others may differ).
I'm not convinced the above provides for a clean interface, but w/o adding new mnemonics that seems to be the best I could come up with.
Kind regards,
Michael