First, here's a safer version of the button code that will handle multi-word filter names..
@nofilenamequoting
@Set f={dlgstringS|Enter a filter name...|Today}
Select "{$f}" FILTER
@Set h={dlgstringS|Enter a highlight name...|HiRed}
Properties SetLabel="{$h}"
Select DESELECT "{$f}" FILTER
Re my config, there is not much to see. I use the stock standard Menu and Operations toolbars and I add 3 extra user menu buttons to the File Display toolbar. I also keep a floating toolbar with a whole slew of buttons and menus docked to the left of my primary display. Two of the extra File Display menus are for quick links to folders. In the screenshot, one of these menus is expanded and you can also see the docked floating bar which has buttons that are used for many things - e.g. triggering applications, displaying a variety of drop down menus to do "stuff", backing up my Opus config, restarting Opus, etc..
In my experience, you build up a configuration over time that suits the way you work, and since everyone works differently it is important to have the flexibility that Opus affords its end users. People are continually contributing interesting ideas and sharing code samples on these forums, and as long as you are prepared to have a go it's generally possible to adapt examples to do what you want. It is easy to back up and restore configs so you can safely experiment (even when you are not 100% sure what you are doing!), and help is always readily available via the manual and assistance from the developers and other forum users.
Regards, AB
