Notepad++ v8.5 is Released
-
@Graham-Norris said in Notepad++ v8.5 is Released:
Is this the mythical perfect release?
Nope. Many users are unhappy with the result of number 4.
Although, to be fair, that’s rather a distinctly separate and optional part of the release, so, does it count? -
@PeterJones said in Notepad++ v8.5 is Released:
The usermanual github has been updated to document the new features, so if you wouldn’t mind making a new Online User Manual release, that would be great.
Done.
However, auto-update won’t be triggered for v8.5 due to several complains about new context menu for hijacking system registry key.
v8.5.1 will be released as soon as the new replacement is ready.
But then we will surely release v3.6 for npp-user-manual.org when v8.5.1 new features is updated in it.
Thank you Peter for all the update in user manual!
-
@donho
Was this change only for Windows 11? Does “#4” in v8.5 have any effect for Windows 10 users?So would v8.5.1 even be different for Windows 10 users?
-
@ImSpecial said in Notepad++ v8.5 is Released:
So would v8.5.1 even be different for Windows 10 users?
I’m pretty sure that 8.5.1 will offer more changes than an updated Win11 context menu thingy. So “Yes” is the anwer to your question.
-
@ImSpecial said in Notepad++ v8.5 is Released:
Was this change only for Windows 11?
For #4 yes.
Does “#4” in v8.5 have any effect for Windows 10 users?
No.
-
Npp version 8.5.0 (the right one in the picture) no longer shows end-of-line annotations.
Npp version 8.4.9 (the left one in the picture) works as expected. -
-
@Ekopalypse said in Notepad++ v8.5 is Released:
Npp version 8.5.0 (the right one in the picture) no longer shows end-of-line annotations.
Npp version 8.4.9 (the left one in the picture) works as expected.The annotation is triggered by script right? Because Notepad++ doesn’t have annotation natively.
-
yes, but no, it is triggered by a plugin and not by a script.
But 8.5.18.5 returned 0x80005 as its version number instead of the expected 0x801f4
-
@Ekopalypse said in Notepad++ v8.5 is Released:
8.5 returned 0x80005 as its version number instead of the expected 0x801f4
The way I understand it from HERE, what you are getting is consistent with calling NPPM_GETNPPVERSION with ADD_ZERO_PADDING = false; is this what you are doing?
-
Thanks for looking over it, yes, before I just took the return value without sending the padding, now I do that. These are the kind of problems that take too much time just because someone didn’t read the doc properly… phew.
-
-