Bad contrast theme bugs and installer bug
I love Notepad++ though there is an annoying (at least) hard-coded colors in to the program that create really bad contrast as well as an installer bug:
- Notepad++ installer forgets installation path. I always do custom installations and never use the Program Files garbage folder.
- Notepad++ find window instance count number has very poor contrast / can not be configured.
- Notepad++ Plugins Admin anchor (bottom right) has poor contrast.
The count instance in the find window is the worst. I use dark mode as I have to work some ~14 hours a day in front of my computer - no vacations, no extra days off, no weekends - EVER. So dark mode is important to not being blinded by the EVERYTHING MUST BE MAX LIGHT BRIGHTNESS QUESTION NOTHING mentality. If you want to be blind, that is your choice.
I am using:
- Notepad++ 8.4.8.
- Notepad++ Obsidian theme.
- WindowBlinds program.
- A mildly modified copy of the Fl8t theme (happy to share it with others).
Here is a picture of that horrible contrast:
![Notepad++ Bad Contrast in Find Window]( image url)
Application installers that don’t remember the installation path is really more of an annoyance though it’s nice when I don’t have to waste another 20 seconds to correct it.
So can we please get a fix for being able to change the color of anchors in Notepad++? I did go through the theme settings (there are a lot) and I’ll admit there is a chance that I missed it (not going through the 98% different language configurations).
It sounds like you have three valid issues.
As this forum tries to make clear in the Please Read Before Posting and other FAQs it links to, we cannot change the codebase for you – we are a Community of fellow Notepad++ users. We have a FAQ entry that explains where to make feature requests and bug reports.
Regarding the installer: it surprises me that it’s still not remembering your path; they updated the installer last year, and it was supposed to fix that bug.
When you put in your issues, please create three separate issues , because they require three different fixes, and need to be tracked separately. Make sure you include your Debug Info and follow the rest of the “issue” template for all three. And so that people who find this post can see what ended up happening, it would be polite for you to paste a link to all three of the issues in reply to this topic. (Also, if you phrase them as polite requests rather than using words like “garbage” and YELLING IN ALL CAPS, you are much more likely to stay on the developers’ good side, and avoid antagonizing them into not making the fixes.)
@PeterJones The installation path bug, with a twist:
I’ve been slaughtering bugs like it’s Starship Troopers this morning so I’ve been trying to not get side-tracked by stuff.
Here is the contrast color bug report:
I am usually a bit more thorough so please forgive me if I missed anything.
Just on a side note, I’m mentioning politely, you forgot to submit your Debug information, that you can find in the menu selections of:
?->Debug Info...->Copy debug info into clipboard. This will give them most all the information they’ll need and can contact you if more is needed. You should put it in those posts in github, for sure, and you can also include it here, if you wish, but definitely there. :)
you forgot to submit your Debug information
Well…it doesn’t actually help too much in this case because the complaint is about N++ behavior that has existed back to the beginning of time (defined as: as long as I can remember – I suppose that makes it a personal beginning of time). So, it’s not like knowing what version the OP has is important. But yes, technically to be correct, all submitted issues should have Debug Info included.
This post is deleted!