Most of you people know me me to be an overly verbose SOB… so especially with multiple beers in me, I’ll try to keep tis brief - but FULLY expect to fail :
First - check out the original beta announcement on scripting, it does a pretty clear job of spelling out the different implementations for scripting support in v11.
Second - my explanation of scripting in v11 in three main parts:
Part 1 :
Support for Script Functions, which basically allow you to write scripts directly into a button or hotkey where the data you have to work with is available through the ClickData object Opus passes to the ~main-ish function defined in the button. This is essentially limited to on-demand user driven use-cases - i.e. you click a button or hotkey to make it “go”. This is what I think you were expecting…
Support for Script Add-Ins that need to be “installed” to Opus… Script Add-Ins come in two basic flavors:
As “event handlers”, where GPSoft has outlined a set of “events” that Opus will fire upon performing common actions - and which a Script Add-In can then be written to respond to. This is the case here… where among the “events” GPSoft has defined, there is an OnBeforeFolderChange event that my script registers as a handler for. I selected this event in order to be able to have my script be able to access information about the folder that is about to be opened so that I can modify the behavior that Opus would normally exhibit. In this case, BEFORE Opus opens the folder in the same tab as it would normally do - the script checks the folder path about to be opened against a set of user-configurable folder paths in order to do something different, which in your case seemed to be to open the folder in a new tab instead of the current tab… You can specify the “target folders” for which this should occur by following the directions I mentioned below about opening the Preferences / Toolbars / Scripts page (where you can drag and drop the script package to in order to “install” it), highlighting the installed script, and clicking on it’s “Configure” button. That button should open a dialog where you will see two configurable script options. One is the DEBUG option which can be set to True to enable logging to the Opus Output Window, and the other is the OpenNewtabList option which - if you double click on it - will let you type or paste in a line separated list of folder paths which you would want the script to open in new tabs…
This is the beauty of the “event handler” type of Script Add-In… it registers as a handler to respond to specific “events” which Opus will always generates. You don’t have to click a button to turn it “on” or to use it. It’s always waiting in the background, waiting for Opus to pass it information to decide what to do with when the event it’s written to respond to takes place… I’ll post a few videos tonight or tomorrow for some of the things I’ve written if that would help.
As opposed to the “event handler” I just described, Opus also allows us to write scripts that actually add raw commands to Opus. They are a bit like User-defined Commands that you can create directly in Opus, and become available in the button and hotkey edit dialogs just as normal internal Opus commands. They are different from User-defined Commands in that they have the power of the supported scripting language in which they are written in order to control what you want it to do… You’d actually make use of these in the same way as you would any internal or User-defined Commands… in buttons or hotkeys etc. As opposed to writing the first type of “script function” mentioned above, these are useful when you want to your capability available for use just like any other internal Opus function - and might provide some additional data and methods to work with than what is made available to “script functions” via the ClickData object I mentioned above.
MULTIPLE PINTS IN AT THE MOMENT… so hope this helps rather than hurt.
Bottom line - to test whether this is of use to you (maybe I misunderstood what you were looking for)… “install” the script as instructed via Prefs, then click on the scripts ‘Configure’ button… Double-click on the ‘OpenNewtabList’ option shown in the configuration dialog and type in several folder paths. What should happen is that anytime you click on the folder specified in the full folder path(s) you add to this option, the folder should be opened in a new tab without having to explicitly do so using a button or qualifier key, etc.
Is this not the main part of what you asked could be done?