Customize -> Commands ... add a time line slider for Opus cmd history tracking?

Help & Support
1

Version: Directory Opus 13.22, 64bit, Windows 10

Location: Customize -> Commands tab

  • Background info: When trying to keep on top of what new commands have been introduced after a Opus update patch, a time line of sorts would make new features very much easier to spot.

  • Request: Please consider adding a time line slider to the Customize → Commands tab - like on the one under Customize → Default Toolbars - , as a filter option to let us check for new commands i.e. when they were added.

Obviously this is not an essential suggestion, but it could be a nifty QOL feature, IMO.

FYI Tangent: my JavaScript solution to finding Opus cmds unused in my custom menus…

  • I had this idea a week or so ago and was wondering if there was a way for me so solve the issue of tracking down new Opus cmds (commands), automating this process somehow.
  • Conveniently all the toolbars, custom menus etc. are separate files in XML format. So why not directly manipulate/edit/update/ those?

Question: Opus apparently uses an internal list to show all the “official” internal Opus commands in the Customize → Commands tab… I had hoped the list would be in an external XML file like all the toolbars. Or is there an external file I am missing with all the Opus cmds ?

  • So I created a new custom “menu” toolbar where I replicated the Customize → Commands tab menu structure, by drap-n-dropping each command into that toolbar. This way I had a complete list of all official Opus cmds in a convenient custom toolbar I named “Opus13-AllCmds”.
  • Now using UltraEdit’s JavaScript implementation (I could have done it Opus, but editing programming files i.e. XML is more convenient in UE, for obvious reasons.) I wrote a script that loads Opus13-AllCmds into a JavaScript string variable. I then parsed the <instruction> lines (= the Opus cmds)… giving me a complete list of the official exact cmds.
  • Next I loaded all my custom toolbars, those I use in every lister: AE-ListerMenu, AE-Pathbar, AE-Toolbar… into JavaScript strings as well, and then went through the list of official cmds and searched for them in my toolbars.
  • When I found a cmd, meaning I actually already use this official command in my menu, I go into the Opus13-AllCmds XML code and delete that command entry, i.e. the <button code “block” that cmd is in.
  • I repeat this for all commands.
  • In the end I save a new custom menu toolbar called: “Opus13-AllCmds-unused-by-AEtb”… this toolbar only shows the official Opus cmds I am not using.
  • I then load/show Opus13-AllCmds-unused-by-AEtb in a lister and use it as a starting point to update my AE-toolbars (drag-n-drop in Customize mode), knowing exactly what Opus commands are new to my toolbars and should thus be updated.
  • After updating my AE-toolbars, I can run the script again to re-check if I actually have used all official Opus commands.

This worked nicely… and helped me find quite a few new Opus cmds I had not added to my custom menus yet, coming from Opus 12.

Thanks, AEon