|
|
Post by Robert on May 27, 2024 17:02:21 GMT -5
Yes, but there are primary commands that only work in Edit or only in FM. I didn't want to blur the distinction; otherwise the data returned from this function is not as useful.
Examples: ALIGN is edit only, CD is FM only, and BOTTOM is both Edit/FM.
R
|
|
|
|
Post by Robert on May 27, 2024 17:30:04 GMT -5
The file ObjPCmdT.inc appears to have a primary command OPENWITH that is neither primary nor FM.
R
|
|
|
|
Post by George on May 28, 2024 10:53:44 GMT -5
Robert: Sheesh! You're only trying to locate possible collisions, whether the command collision is an Edit only or an FM only makes no difference. If the Macro/SET alias remains, it's a future possible problem for the user.
Maybe all these should just be called 'Reserved Names' - it would be a lot simpler.
Yes, OPENWITH is in there for INTERNAL use. There are also secret operands for many Primary commands that are only used internally.
Similarly, the Line command table has entries that aren't line commands, but needed to support macro handling.
Please just ignore stuff like that. Discussing whether doing things that way is good or bad design is moot. They're in there, they work, and unless someone wants to rewrite the affected code, there's nothing is to be gained by trying to understand the need for them.
George
|
|
|
|
Post by Robert on May 28, 2024 11:16:11 GMT -5
I didn't say it was good or bad, only that OPENWITH was present. Since I am trying to understand the source code without your help, I have no way knowing whether it was intentional or a forgotten entry. I was trying to be responsible by notifying you. I am sorry you felt this was a sheesh worthy event.
R
|
|
|
|
Post by George on May 28, 2024 13:03:16 GMT -5
You got me, sorry. I just didn't want to get into explaining some of the more obscure internals. Because so many of SPFLite's commands pass off control to other commands, they sometimes have to pass extra info along, and use internal operands to do so. It's just simpler that way.
George
|
|
