Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Loss of Current Screen with Save function (Ctrl+s) #539

Closed
hpwamr opened this issue Jul 8, 2018 · 2 comments
Closed

Loss of Current Screen with Save function (Ctrl+s) #539

hpwamr opened this issue Jul 8, 2018 · 2 comments
Labels

Comments

@hpwamr
Copy link
Collaborator

hpwamr commented Jul 8, 2018

Hello @RaiKoHoff,
I encountered an annoying problem with the save function ("Ctrl + s"), when I was working on long lines.
I made changes on very long lines (for example, pos. 500) and when I saved my work, each time, I lost my current screen because NP3 jumped to the beginning of the line (pos. 0). 🤔
After a while, it became very annoying. 😁

TXT_Test_20_Long_Lines.txt

@hpwamr hpwamr changed the title Loos of Current Screen with Save function (Ctrl+s) Loss of Current Screen with Save function (Ctrl+s) Jul 8, 2018
@RaiKoHoff
Copy link
Collaborator

Seems to be correlated to changes made between 26th and 28th of April :-/

RaiKoHoff added a commit that referenced this issue Jul 9, 2018
@hpwamr
Copy link
Collaborator Author

hpwamr commented Jul 9, 2018

Tested : Notepad3 (64-bit) X_MUI v4.18.709.1026
Issue corrected. 👍 ❤️
As far as I am concerned, this issue may be closed....

@hpwamr hpwamr closed this as completed Jul 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants