Increase contrast of binder arrows

I don’t really understand why the beta install is different, but I will investigate. The path to the Scrivener executable seems irrelevant to me. It’s all about the relative path from the QSS-stylesheet to the icons in the Icons Folder.

On testing, I find the current version with the relative paths: “./icons/branch_open_white.svg” and “./icons/branch_closed_white.svg” works in beta 3.1.5.0:

The Theme has be to imported and loaded, instead of loaded from file. After importing, you’ll have to select the theme from the menu and restart Scrivener to make the Theme show, otherwise you’re still looking at the old version of the Theme. Make sure you’ve restarted the beta version by checking its version number.

(Actually, the Theme with a hard-coded username in the QSS, and the forward slashes in the path , also works as expected.)

But… hold your horses. I’m getting mixed results, I don’t understand yet. The jury is still out…

The icons referencing the Resource Library are not the open and close icons for the branches. Only the last two rules in the QSS are addressing those. The icons use a relative path from the QSS-stylesheet to the Icons folder.

Hi Antoni, well, I thought I had done that import, and that the result was to put the theme renamed-zip in the folder accessed from the menu to show imported themes. I worked on my variants by editing the css-actually file in there, which is is readily done via 7-zip, which can let you edit and save changes, not altering the zip type. This was proper enough, as results showed, but I wasn’t re-importing actually, so…

You’re probably aware that there are many more permutations possible in real-programming-land than we’re discussing, so all bets are off on any assumptions without seeing that internal code.

I saw a much cleaner solution if we have to have a hard path, but let’s see if I can simply get your ./ path version to work first. If it would, then it should also for the Program Files destined install of ordinary Scrivener as well.

I’m away from the laptop of experiments, but will let you know how it comes out – just wanted to gain you a little peace on your later Sunday hours :slight_smile:

Clive

I’ve posted the issue as a bug, as I’ve gotten a result one time, but could never repeat it.

Both the relative path and an absolute path in the QSS work in 3.1.4.1, but not in 3.1.5.1 B3.
It may be connected to the SVG-files, resolving URLs or rights to access files in the imported themes folder.

I do hope this issue will be resolved.

Going to watch a movie now. :grinning:

2 Likes

Following @tiho_d’s help, I’ve corrected the Theme and the Readme.txt file.
Following the instructions in the Readme, this should now work for everyone.
If you’re using the 3.1.5.1 Beta, you should still just follow the instructions in the Readme file. :slight_smile:
Download the zip-file in the original post of the Theme.

Antoni,
Thanks so much for this theme. Best I’ve seen for someone who turns screen intensity down. (Like me.)

I can now see toolbar icons much better but how can I tweak the size of the arrow-icons? They look great in the screenshot you provided but when I install it, the arrows show up about 1/2 that size.

Oh, play with the extra spacing and line height of the Binder in the Appearance Options for the Binder.
There should be a setting the gives the SVG icons enough room to grow. :wink:

I have set the “Binder item extra indent” at 5 px… You could go up to twenty. See what works best for you.

Hope this Helps

Oh, crap!
Didn’t even think about it being a setting in Options. I messed with numbers in the QSS file and didn’t see any change except an occasional error message from Scrivener.
Perfect.
Thanks

How can I edit the the dropdown arrows in the Binder so the arrows are more visible (not transpaarent) wherein I have to squint to see if there is an arrow there or not?
Thank you

You will find some good tips above, in the existing discussion on this matter, as well as links to themes which can radically change them, and instructions on how to make your own themes (if you are so inclined).

1 Like

Hello :slight_smile: I’m having a bit of an issue with your method of correcting the arrow color in a theme and I hope you can help. Generally, I use the standard dark theme and enjoy it, but I can’t see the damn arrows to save my life lol, so I was really excited when I found this post, but… everything works exactly as it should except the arrows completely disappear rather than change. I even tried Tn’s theme further down and the same thing happens. Arrows just… gone. It all still functions, but the icons are not showing at all.

Now, I’m not new to modding things (I’d hoped to just adapt the arrows into the normal dark theme) and checked to be sure the icons were in the right spot, which they are, but I’m not exactly sure what to try next. Was there some update between summer 2023 and now that might have broken things? Is there some other setting in Options I might have on/off that’s causing the problem? Seems highly unlikely but idk lol any help would be greatly appreciated!

I noticed this issue when starting a Project with an updated Theme from the SCRVX-file. Apparently, the filepath to the icons is different in that case. When I use Windows Jumplist from the taskbar, I have the same issue.

But when I close Scrivener, and restart by just clicking the icon in the taskbar, and Scrivener opens the last opened Project, everything works fine.

I don’t know what file path to use in the cases it doesn’t work. I have icons relative to the application, and relative to the Application Support Folder.

I tested with the icons relative to the SCRVX- file, and that seems to work as well, when double-clicking the SCRVX-file.

When you can edit the QSS-Stylesheet, updating the path to the icons can contain your Windows Username, and then you can place them wherever you like.

Hope this helps

1 Like

Thanks for the help and, yes, it does indeed seem to be an issue with opening from the file vs the icon. I’ve just started using the icon to open things for now, but maybe I’ll poke around in the future when I get some time.