What's an efficient workflow for developing commands?


The Command Editor window lacks a Run button for running the command I am currently working on. As a result, my workflow when developing a complicated command goes something like this:

  1. Right-click menu bar, Customize > User-defined Commands > double click [my current command] > Make a change
  2. Click OK, and OK again to get back to Directory Opus
  3. Test the change I made
  4. Go back to step one.

This is quite painful. I tried using the CLI to test my commands but:

@set prefix={dlgstring|Enter prefix for thse files}
Unknown command

So... what am I missing? There must be a better way to do this! thank you :slight_smile:

You can run a button while in Customize mode by shift-clicking it, if that helps.

It sure does! Looking for more tips, but that alone is going to save me heaps of time.

Turning on Preferences / Toolbars / Options / Alt-Click to edit Toolbar buttons (and the Minimize Customize Dialog option below it) is also a big time-saver if you want a way to quickly edit a button and then leave Customize mode.

Tip of the week that... superb :slight_smile:

Nice! Although slightly less useful for me because I don't write the script into the button, but as a standlaone command which I then bind to a button.

A very useful tip for me thank you :slight_smile:
I am wondering if there is an way to disable the "allways on the top" option of customizations windows ?

There isn't. Menus are always on top so the things which edit parts of them need to be as well.