Post by Stefan on Dec 1, 2022 5:28:24 GMT -5
George,
A while back I asked for the MAX versions to be included in the (TRACK) concept.
You explained that this wasn't practical and I built a macro around it.
It's code is rather converluted and still imperfect when dealing with pending line commands. In short - it's overkill.
On second thoughts, it occurs to me that there's potentially a much simpler and more universally useful solution.
You gave us (Track) and (TrackF).
Suggestion:
How about a (TrackC) primitive.
This would effectively "create" a track point, in the same way as a "SET TRACK.xxx = Y" command.
Effectively it could be used in KEYMAPs before any command to create a return point.
So my initial wish for UP MAX and DOWN MAX to be trackable, becomes a simple matter of replacing UP MAX with (TrackC)UP MAX , etc.
Doable?
PS: We'll need to retain the SET TRACK.xxxx = Y option for commands initiated from the comamnd line rather than KEYMAPs.
