[Feature Request] word wrap improvement: make the current line visible after word wrap state change

[25minutes]

After I trun on word wrap, the current line often moves out of the display area. I have to scroll the document to find it again. It would be convenient if it can automatilly "goto" the current line after word wrap state change.

[hpwamr]

Hello @25minutes ,

I think this problem was solved with one of the "Notepad3_beta" versions? 🤔

Question: Have you tried with the latest RC version: "Notepad3 6.23.718.1_rc"?

---

Feel free to test the "BETA/RC PortableApps", version "Notepad3Portable_6.23.718.1_rc.paf" or newer, see in issue #1129.

• Notepad3Portable_6.23.718.1_rc.paf.exe.7z -s

"Notepad3Portable BETA/RC PortableApps" version can be used with or without ".7z" extension.

Also, feel free to test the "BETA/RC Setup", version "Notepad3_6.23.718.1_rc_Setup" or newer, see the 2nd list in issue #1129.

Comments and suggestions are welcome... 😃

[25minutes]

No, the latest RC version doesn't ensure currrent line is visible after word wrap state change.

I attach the test file and screenshots for your reference. My testing shows:

• Line52 is the current line before word wrap.
• Line52 is no longer in the display area after word wrap.

As you may have different windows size, the result may not be the same at your side. Anyway, the basic idea is the same, the current line may not be visible with current implementation.

test.txt

[hpwamr]

Hello @25minutes ,
Thanks for the test file: test.txt
Yes, it appears that the behavior of Word Warp has changed after version Notepad3Portable_5.21.227.1.paf.exe.7z. 🤔

[hpwamr]

Hello @25minutes ,

Feel free to test the "BETA/RC PortableApps", version "Notepad3Portable_6.24.527.1_rc3.paf" or newer, see in issue #1129.

• Notepad3Portable_6.24.527.1_rc3.paf.exe.7z -s

"Notepad3Portable BETA/RC PortableApps" version can be used with or without ".7z" extension.

Also, feel free to test the "BETA/RC Setup", version "Notepad3_6.24.527.1_rc3_Setup" or newer, see the 2nd list in issue #1129.

Comments and suggestions are welcome... 😃