

- #HOW TO SCROLL DOWN SHORTCUT ON NOTEPAD++ WINDOWS 10 PORTABLE#
- #HOW TO SCROLL DOWN SHORTCUT ON NOTEPAD++ WINDOWS 10 CODE#
(Good) UI scaling support? Dynamic refresh-rate support? eGPU support? Thunderbolt? Support for modern biometric authenticators like Windows Hello? Support for booting off a portable volume? Handwriting recognition in arbitrary apps? Basically 80% of accessibility features being finally pushed down into older software (with “dark mode” as a side effect)? > Operating system for majority of users are feature complete for years

Especially if you’re a developer working on programs that are supposed to handle said characters. Maybe there are people who are impressed with such things or expect that these should be here but I'm definitely not.Īre you suggesting that a desktop OS shouldn’t support an input method for standardized Unicode characters? That would be incredibly annoying.

And for quite some time I'm having a feeling that all of this is being done only to provide an illusion that someone does something, so the all decision-making people, CEOs would be satisfied that a product was improved. All of this is often presented as some breakthrough "experiences" that are about to fundamentally change user life - forever.

But it can be done anywhere.Įmoji or gif support in desktop OS, sidebars or notification centers, all sorts of content or tasks suggestions, virtual assistants that are limited to only few languages, countless GUI changes or application redesigns that makes no sense or make the workflow worse. Perhaps the preexisting familiarity with a particular OS would be the only factor determining how comfortably user get the job done. Operating system for majority of users are feature complete for years and for most common tasks it would make no difference if work would be done on Windows, macOS or some Linux distribution. Don't even try to resize the window with a big file open (< 1 FPS)ĮDIT: Note that I haven't even complained about new features or anything, just the previous, basic features still working correctly. Both have SIGNIFICANT lag in the new one. I've grabbed a notepad.exe from Windows XP SP3 in comparison, no problems there, scrolling and editing is instant. another first party piece of software that ignores the "no animations" setting in windows 215k lines loaded, moving the window itself is choppy now? HOW the animation has to "catch up" when grabbing the scroll bar handle and moving it quickly the animation runs at 60Hz even on a high refresh rate screen, so it looks choppy Any amount of delay is too much in notepad THEY ANIMATED THE SCROLLING OMG PLEASE DONT DO THIS (especially when grabbing the scroll bar handle). It consistently starts slower than Notepad3 while having substantially fewer features to load (and also slower than the old Notepad of course) It's nice to see the wind change on that, even if it took a decade or two.ġ0 minute QA because they don't seem to have done it:
#HOW TO SCROLL DOWN SHORTCUT ON NOTEPAD++ WINDOWS 10 CODE#
Of course the compat issues were real (you could view reports on which obscure apps hooked into this or that internal code of cmd.exe or Notepad and would break), but I always though they served as a nice justification for whichever investments were being made at the time: certainly not Notepad. It would surface on internal mail threads from time to time as a joke or a bitter reflection on bureaucracy, and if I recall a VP once chimed in to say they had looked at it, and sadly none of it could be committed due to backwards compatibility issues. Single undo, unicode support, unix LF support, etc, etc.įor Notepad a frustrated engineer had produced a change-set to fix all of them, and it had sat there attached to the bug for some time. I don't know if anyone even owned Notepad or any other older inbox apps like the command prompt, but the issues were pretty well understood and WONTFIXed. Every issue that gets complained about online - and many more - are in there, and have been for a long time, marked WONTFIX due to a potential compatibility break, lack of priority, or some other policy reason. I worked on Windows back in 2014, probably the most surprising thing joining there out of college was looking through the bug database.
