Overview
Created to match the default Windows 11 File Explorer as closely as possible.
Also requires icon pack, attached to this post. It's an adapted version of this icon pack by Skinz: https://resource.dopus.com/t/fluent-style-icon-set/46558 - Extra icons sourced from Segoe Fluent Icons Font and shell32.dll.
In Opus, go to Preferences > Colours and Fonts > Themes > Import, and select the “Windows 11 Default Style.dlt”
Still in the preferences window, go to Toolbars > Icons > Import, and select “Windows 11 Default Icons.dis”. With the new “Windows 11 Default Icons” entry selected, hit the “Move Up” button to move it to the top of the list.
Go to Backup and Restore > Restore configuration > Locate "Windows 11 Default Config.ocb" and click "Restore"
The favorites bar that we enable to be viewable did disappear for me too when I added this theme. It was a quick fix though-- right click in toolbar area at top, hold curser of Toolbars, then click Favorites Bar
You mean when you installed the whole config backup (.OCB), not the theme (.DLT)?
Themes cannot affect which toolbars are open.
Loading someone’s config backup will replace all of your Opus settings with the other person’s, and should almost never be done unless you really want that for some reason.
The .dlt theme and .dis icon pack should both be safe to try, but we recommend against installing .ocb config backups from other people, as they will replace your whole config, not only the cosmetic settings.
This is not only an awesome theme but also a helpful set of configurations that complement my workflow. What a pleasant surprise. Thank you for sharing!
One of many reasons we recommend against installing other people's complete config backups.
Maybe we need to start deleting them from posts, as they're causing so many problems, even with warnings added to the posts they are in.
Theme (.dlt) files only modify cosmetic settings and are safe to install, but full config backups (.ocb) change far too many settings. It doesn't make sense to load someone else's entire config.
Btw, @plomasney, I also see a privacy and security risk in sharing the entire config, as it contains sensitive data like file paths/favorites, and possibly even credentials (FTP, SMTP etc.).
