ToolbarPalette : A Command Palette option for Opus

Sent.

v2.0.0 (Jan 13, 2025) :

  • Added support for listing hotkeys.
  • Added support for listing entries in context menus (limited to "All Files and Folders").
  • Added support for a fully customizable right-click menu with predefined variables:
    • Current variables include: $label$, $desc$, $hotkey$, $instr$, $toolbar$, $toolbar_file$, $toolbar_line$, $toolbar_pos$, and $toolbar_group$.
    • The menu comes with two predefined entries to help you understand how to use it.
  • New arguments: EDITMENU, NOFILTER.
  • Added options to define maximum width for columns in the list.
  • Other minor fixes.

The main post has been updated as well.

3 Likes

You've out done yourself! Bravo! This is my new F1 key for dopus!

This is great. Ive 1224 items here, time for clean up!


one request. Which I could likely do myself just not sure how??

under the label column where the menu branches are displayed, can there be a space around the > between the submenus?

it can be hard to read at a glance when its a altogether like a run on sentence.

File>Properties>Set Rating>5 Stars vs
File > Properties > Set Rating > 5 Stars

all the best
x

Thanks.
And yes, you can change the separator in the Script config.

found it, thanks again

Wow, I was JUST going to ask if there was some way to query the menus/toolbars.

I have been using the excellent "FullMenu" toolbar for a while because I like to have as many commands as possible at my fingertips but sometimes I have trouble finding the command I need.

I look forward to trying this, thanks!

Update: Works great so far. Thanks @errante.

If you liked FullMenu, may I toot my own horn and suggest you look at my efforts in this direction.

I installed v2.0.0 on a system where no earlier version has ever run. It failed to start with an error flagged at line 43. Changing that line from

if (!initData.startup || initData.vars.Exists('version') || initData.vars.Get('version') != script_version) initData.vars.Delete('~(search_in_flags|menu|version)');

to

if (!initData.startup || (initData.vars.Exists('version') && initData.vars.Get('version') != script_version)) initData.vars.Delete('~(search_in_flags|menu|version)');

resolves the startup issue.

When I run it, there is a warning message as follows. I haven't looked into it. Is it something I should be concerned about? The toolbar in question works as intended.

ToolbarPalette: WARNING => => Error processing toolbar Floater : Object not a collection

I think it should be instead :
if (!initData.startup || !initData.vars.Exists('version') || initData.vars.Get('version') != script_version) initData.vars.Delete('~(search_in_flags|menu|version)');

Looks like that line is just for facilitate the testing and I forgot to remove it for the release. Thanks.

I'm guessing that the buttons on that toolbar aren't listed by the command, right?
Would you mind sharing that toolbar with me privately?

v2.0.1 (Feb 17, 2025) : Needs at least v13.13.3

  • Fixed an issue when retrieving toolbar info from floating toolbars when include all toolbars was set to false (buttons were loaded fine, but other info retrieval failed).
  • Fixed an error that could occur when installing the command on a computer didn’t have version 1.0.0 previously installed.
  • Fixed an issue where the $hotkey$ variable was not working.
  • Added tooltips for most controls to improve usability.
  • The Edit Menu dialog will now copy variables to the clipboard when clicking on any of them.
  • Other minor corrections.
2 Likes

thank you SO MUCH!!! I've wanted this forever!

Errante, there seems to be a small bug in Toolbar Pallette 2.0.1.

I'm setting TBP to close, when i push ESC, but the setting is going back to normal after every reboot.

I can't see any way for a script to change/revert a value from the Script Config, because those are read-only and set by the user.
I did a quick test, and it doesn't seem to happen here. Do you mean an Opus reboot? Or a computer reboot?

It happens after restarting Opus.

(edited)

Thank you for this - it's incredible!

Right now, however, it doesn't seem that user commands are included in toolbar palette's search. The only existing workaround is to copy user commands to hotkeys, at which point it will be searched for.

However, Assigning a new hotkey to every custom command is rather cumbersome and shouldn't be necessary.

Thank you for your consideration!

I may be getting recent threads confused with each other, but did you have a similar problem with file type settings or something else resetting every restart as well?

It's possible something is blocking your config files from being modified, or restoring old versions of them in the background for some reason. That would explain settings not saving across restarts properly.

As a matter of fact, i do. In aussieboykie's Filetags2 there are two settings that won't stick. I have to reset them, whenever i intend to use them (nearbytab/noconfirm). Not a big issue, but could be related to the other thing.

But what could that be? I'm now on a completely new computer/setup, and don't suspect any of my other applications to interfere. No message in Defender, and the scripts work fine otherwise. Anyway, those two scripts are the only ones i'm aware of, that show those effects.

@abr If I understand correctly, the issue is:

  • in the script configuration, you set that value to true,
  • press OK,
  • restart Opus,
  • reopen the configuration dialog, and the value appears changed to false

Could you come up with a video that can show that?
What happens if you check for the value without restarting Opus? Does the value persist or does it change anyway?
(probably best to do it in its own post, as I don't see how it could be related to this script.)

Yes, that's how it happens. If i don't exit Opus, the value remains, doesn't change back. About the video, not at the moment. I never really used one of those programs that can record those documentation clips, i sometimes even struggle with screenshots, where the dialog window in question disappears, once i click the screenshot combination, depending on the menu type and application.

But in this case there's not much to see anyway. All that happens is that the value jumps back to its initial state, so i might show two screenshots as well, which doesn't reveal much of what's going on.

And regarding the script, yes, i also think that it's not specific to your script, as it also happens in Filetags. But what they (the effects) have in common is, that they all are true/false choices, if that matters.