1) Open read only file in N++
2) Change file with another program (unmark read only with this program and overwrite the file)
3) Go back to N++, you will be prompted that the file has changed and whether you would like to reload or not. if you choose reload, it does not in fact reload the document, but does unread only it.
Has anyone else run into this, or can anyone else confirm this happening on their copy. i can reproduce on both my machines.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Since N++ does warn when a file has been changed externally, it would also be welcome if a warning or question appears when the file is closed in N++ and was not reloaded before.
Because the document's contents in N++ are different from the contents of the external file itself, warning the user about this is as justified as asking if he wants to save a document that was changed inside N++.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Process:
1) Open read only file in N++
2) Change file with another program (unmark read only with this program and overwrite the file)
3) Go back to N++, you will be prompted that the file has changed and whether you would like to reload or not. if you choose reload, it does not in fact reload the document, but does unread only it.
Has anyone else run into this, or can anyone else confirm this happening on their copy. i can reproduce on both my machines.
Well, I have a similar concern.
Since N++ does warn when a file has been changed externally, it would also be welcome if a warning or question appears when the file is closed in N++ and was not reloaded before.
Because the document's contents in N++ are different from the contents of the external file itself, warning the user about this is as justified as asking if he wants to save a document that was changed inside N++.