|
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.
|
|
|
Post by Stefan on Dec 15, 2022 11:48:50 GMT -5
George,
I'm not sure given the flurry of bugs recently, some of which were quite old and well hidden, if you're still considering suggestions.
If you are still up for the odd addition here or there, please consider the above request for a (TrackC) primitive for KeyMap.
Thanks.
|
|
|
Post by George on Dec 15, 2022 12:44:14 GMT -5
Stefan: Somehow I never saw the original post. I'll give it a look. Sounds fairly easy (as always - famous last words)
George
[UPDATE]
OK, it's in the next Beta. It seems to work, but I'm not sure I'm testing it the way you want to use it. Let me know.
[/UPDATE]
|
|