What could be done...
admin wrote:Hm, what's the use of this?
I'm working on a script* and could use this to generate a simple "script" builder by stringing together CIDs.
Alternately, it provides another means of accessing the list of commands, even allowing the possibility of creating custom filtered menus. (Menu of all Copy commands, or Rename commands.)
It would also allow someone to write a script that diffs this information between versions to show what's changed or to create custom cheat sheets for keyboard shortcuts.
Why these are difficult to achieve today...
There is no good way to retrieve the list of commands (with CIDs) via script.
The best solution I can think of is instruct the user to open the List of All Commands, while holding CTRL, copy the contents, close the dialog, and then run the script again. This would need repeated until the clipboard contents matches the expected format, but it would still be impossible to detect if they copied a filtered list of commands.
Another option is a painstakingly slow while loop that collects all commands which return something for Get('MenuCaption', $i).
In either case, this would need repeated each time XY is updated to account for command additions or removals, and that's ignoring the complications from UDCs.
*The script itself is actually a feature request I've held off making. I figured the surest way to get it into XY is to write a script that you can render useless shortly after release.