File Status Auto-Detection has a bad design

[andry81]

File Status Auto-Detection has a bad design

[notdodgeball]

I mean, if you "don't need to know" and hate the popup window then the "Update silently" option is already there. And unless you selected the non default "Enable of all opened files' option, you don't get "infinite modal dialog popups" of "masses of opened files".

npp actually does exactly what you ask for by default, as in, until you focus on a tab, no auto-detection is made.

There is room for improvement of course, mainly highlight the changes using the already implemented Change History feature, instead of simply reloading the file, as it does clear the Change History. Or even a visual/sound clue to notify user of changed docs out of focus.

But calling it bad design without a proper knowledge of the settings provided... The modal windows are actually GOOD design, there is risk of losing work and it needs immediate confirmation from the user. Not everyone is using it in conjunction with git, whose changes you probably want to be displayed and are monitored by a version control anyway. Most users need to be made aware as soon as it happens to inform them the changes they made, if any, will be lost and future changes risk being saved over by the same software with write permissions. For the rest there is "Update silently".

[andry81]

I mean, if you "don't need to know" and hate the popup window then the "Update silently" option is already there. And unless you selected the non default "Enable of all opened files' option, you don't get "infinite modal dialog popups" of "masses of opened files".

And catch another issue with a changes silent overwrite. Did you read #14540 ?

To resolve a collision you have to manually merge changes, there is no other easy way to accomplish this. A files editor must open a file changes comparator UI tool like, for example, WinMerge. There is no any of it. So it keeps be a bad design.

The modal windows are actually GOOD design, there is risk of losing work and it needs immediate confirmation from the user.

Then this is a good time to save both variants of a file if have no time to merge it.

Not everyone is using it in conjunction with git,

This is just an example of escalation the problem. There is other examples, which leads to the same result.

whose changes you probably want to be displayed and are monitored by a version control anyway

The monitored by a version control does not mean what the Editor should not track the changes itself. Even more, it must track, otherwise ppl would lose the immediate work not yet been saved or committed by a version control, isn't it?

For the rest there is "Update silently".

There should not be any of "Update silently", otherwise you would lose the work silently. If you prefer this, then you don't prevent the users to lose their work.