Notepad++ 7.8 Release
-
@donho a regression in 7.8 is explained https://github.com/notepad-plus-plus/notepad-plus-plus/issues/6211
-
Seems like that github issue stands on its own and doesn’t need to be called out here? Regressions happen; not the end of the world. :-)
-
@Alan-Kilborn 7.8 auto update yet not triggered. So it can be stopped at this moment before its wide spread via auto-update.
-
Again, not a huge problem. RC period is over. 7.8 is out. Let it go (IMO).
-
I’ll make it optional in the future release.
-
It’s still a regression (and quite important) though. @SinghRajenM made a good point on it: the binaries contain regression should not be distributed via auto-updater.
Thank you & well done.
Committed in:
https://github.com/notepad-plus-plus/notepad-plus-plus/commit/c16f7bbc1e59e86b4d7650f63a10b8fe47fdaac0Fixed, will be in the next release.
-
@donho said in Notepad++ 7.8 Release:
It’s still a regression (and quite important) though.
…the binaries contain regression should not be distributed via auto-updater.Quite important…hmm…
Perhaps these days “auto updater” is a “bad idea” to have at all…
-
I suppose everyone has features in mind that they consider important. How come you glossed over this one (apparently from Middle-Earth) that might be more important to a quantity of users than some obscure command-line parameter:
@Bilbo47 said in Notepad++ 7.8 Release:
“3. Add “No to all” and “Yes to all” options in Save dialog.”
Regression: The Yes/No/Cancel buttons used to have hotkeys so that single keystrokes could give a command on how to proceed. In 7.8, “Y” and “N” are ignored, while “Escape” still works. This is a showstopper for me; back to 7.7 for that basic usability feature. Also for standard usability, the new “All” buttons need to have their own hotkeys. -
@donho
The global bold thing is a bug. Just check it yourself . . . -
I was under the impression that you have to tick Bold from Font Style as well
if you want to enable the global bold font style.
Am I wrong? -
@Ekopalypse said in Notepad++ 7.8 Release:
I was under the impression that you have to tick Bold from Font Style as well
if you want to enable the global bold font style.
Am I wrong?That’s right. But the problem is different. If Bold and Enable global bold font style are not checked - this is the default setting, right?, some but not all characters and words are thicker, as bold would be selected, but actually bold is not selected. The first screenshot demonstrates this.
Just watch carefully the first screenshot, watch the case keyword, and the punctuation marks like dots, semicolons and commas.
Now keep watching those elements. Make sure the Bold box is checked and check the Enable global bold font style box. You will observe that those elements will be thinner. My question: why are they turning thinner (by the way they should turn thicker in the worst case - but that’s another problem) when the global Bold box is not checked?? IMHO if the global Bold box is not checked nothing should be changing visually if you toggle the Enable global bold font style box.
-
P.S. instead of: Make sure the Bold box is checked
my intention was to write: Make sure the Bold box is not checkedsorry!
-
@Zsolt-Kántor said in Notepad++ 7.8 Release:
My question: why are they turning thinner
Because you told it to. Those letters started bold (because that was the syntax highlighting for
casestatements), and you set it to override any bold settings with bold=false; so it did;casewould normally be bold, so it turned bold off. -
That’s right. But the problem is different.
Ah, ok, sorry for confusion, I guess @PeterJones said it right.
To summarize my understanding:
If both, Bold and Enable global bold font style areuncheckedthen
the styling settings from the language are used.If both, Bold and Enable global bold font style are
checkedthen
everything will bebold.If Bold is
uncheckedbut Enable global bold font style ischeckedthen
everything will NOT bebold. -
@PeterJones @Ekopalypse
Yes, both of you are right. Sorry for the misleading posts.
I checked and found that (at least with C) syntax highlight makes the keywords and other punctuation marks Bold by default. -
@donho said in Notepad++ 7.8 Release:
I’ll make it optional in the future release.
I just downgraded from 7.8 to 7.7.1 after reading this. When you do implement this option, please let me know so that I’ll know to update.
-
-
@SinghRajenM I noticed the same issue today, but at first I thought it had to do with my homebrew MSI installer. I created my own debugger redirect a while ago when Notepad++ didn’t have the ability to do that. If it helps… source code and binaries are available if anybody is interested.
-
@Bilbo47 said in Notepad++ 7.8 Release:
“3. Add “No to all” and “Yes to all” options in Save dialog.”
Regression: The Yes/No/Cancel buttons used to have hotkeys so that single keystrokes could give a command on how to proceed. In 7.8, “Y” and “N” are ignored, while “Escape” still works. This is a showstopper for me; back to 7.7 for that basic usability feature. Also for standard usability, the new “All” buttons need to have their own hotkeys.
It appears the new “X to all” buttons are available only after the “Close All” command; in case of the “Close” command, they are greyed out. User interface principles say that buttons that are never available in certain circumstances should not even be visible in those circumstances. If “Close” and “Close All” are going to be two separate commands, then the corresponding dialog functionality/discoverability should also be different. If “X to all” is going to be not-available after “Close” then the “All” buttons should be not-visible after “Close”. Or, if “X to all” is going to be available after “Close” then “Close All” should not be a separate command. In short, the decision of all-versus-one should be made only once, or should be made available as often as possible. But showing that different functionality is available only if User backs up and starts over, that’s just maddening.
From experience, custom buttons can be added to the Windows-standard Common Dialogs instead of writing custom dialogs; it just takes some more subclassing and API work to do so.
Agree with Bilbo47. Need the keyboard hotkeys back on the save and close dialogs. I did not realize how frequently I used them until now.
LOVE having the options of Yes to All (which I believe the standard hotkey on that is A) and No to All, though! Was very excited to see that when I am closing a large number of files that I do NOT wish to save, I no longer have to hold down the “N” key until they all close!
Thanks!!!
-
Syntax highlighting on SQL files has a small glitch. This problem existed in the previous version of notepad++:
All lines after “set column” appear with string colours. It appears the 2nd ’ character is not being correctly interpreted.
