Notepad++ release 8.6.9
-
Typo at 12, should be “Show All Characters” (s missing)
-
After updating, my toolbar has increased in size. The icons (I use “Standard icons: small”) haven’t changed, but the spacing between them has apparently increased.
- Enhance the quality of Fluent toolbar icon sets for different DPI settings. (Fix #15253)
Could this have anything to do with it?
-
@TBugReporter said in Notepad++ release 8.6.9:
After updating, my toolbar has increased in size. The icons (I use “Standard icons: small”) haven’t changed, but the spacing between them has apparently increased.
Same problem here.
[EDIT]
Seems to be connected with CustomizeToolbar plugin. When I rename the folder of this plugin so that it won’t be loaded by Notepad++, the large icon problem is gone.
[/EDIT] -
@datatraveller1 Geat new feature, by the way.
-
@TBugReporter @dinkumoil
If you have a problem with CustomizeToolbar please read the issue:
https://github.com/notepad-plus-plus/notepad-plus-plus/issues/15440
With minimal effort you can achieve small icons and a new multi-selection feature for the Show All Characters button (via context menu). -
@ArkadiuszMichalski
Thanks a lot for hinting to this workaround. Works like a charm. -
FYI, auto-update is triggered for v8.6.9.
-
Hi @donho,
will you consider updating the wingup with about 8 PRs for next realease?
/BR, Mattes -
A minor bug as the update is processed, from the “?” dropdown.
The DLG box for consent ends up underneath the in-progress dialog. The in-progress reaches 100% and then churns. The consent popup should land in front of in progress.
Might could be you solicit consent, and the progress dialog is updated and fronted after? Or the consent lands behind the various selection pages (folder, etc.) before the progress dialog lands?
I sat staring at the 100% box for a bit wondering why nothing happens… :(
thanks for your attention to the program
-
@abitawoods1 said in Notepad++ release 8.6.9:
The DLG box for consent ends up underneath the in-progress dialog. The in-progress reaches 100% and then churns.
Both problems should have already been fixed.
So it should be ok from the next version onward (probably a v8.7).
More e.g. here: GitHub issue #15507 . -