Save on deactivate

[ProgerXP]

Add a new setting (default off): if enabled, when application loses focus - current file is saved, unless it's unnamed (wasn't yet saved). This is fully equivalent to calling File > Save manually.

Add corresponding menu item Save On Lose Focus under File > Read Only. When called, shows a similar dialog to File Change Notification except there are 2 radio buttons only: Don't save and Save. Reset if a new file is opened is also present (if checked - when new file is opened or created, sets Don't save automatically). When Save is active, that menu item displays a checkbox. It's generally similar to File Change Notification.

Also, rename item Read Only to Read-Only.

[cshnik]

When called, shows a similar dialog to File Change Notification except there are 2 radio buttons only: Don't save and Save.

It's generally similar to File Change Notification.

FCN configuration dialog allow user to select required mode when the feature is active (Display message/Auto-reload(unmodified)) or disable it.
Implementation of the same configuration dialog looks excess for "Save On Lose Focus" feature since it is assumed to have only 2 modes: ON/OFF. It should have the same switching mechanism as "Insert Tabs as Spaces", "Auto Indent Text", "Reuse Window": corresponding menu item has(has no) checkmark when feature is ON(OFF). There is no additional tuning available for these features and the same UI behavior shared for them will allow to keep application UI clean and smooth.
Please confirm if configuration dialog with 2 radio buttons is still required.

[ProgerXP]

Implementation of the same configuration dialog looks excess for "Save On Lose Focus" feature since it is assumed to have only 2 modes: ON/OFF.

No, it also has this checkbox: Reset if a new file is opened
That's why either a dialog is necessary or a 2 level menu which is less convnient.

[cshnik]

No, it also has this checkbox: Reset if a new file is opened
That's why either a dialog is necessary or a 2 level menu which is less convnient.

OK. Just a thought, "Esc Key Function" and "Evaluate Math Expressions" looks near the same:

Save On Lose Focus>
Disabled
Enabled
Reset on file open

[ProgerXP]

Okay, let's make it a submenu with 3 options:

Disabled
Enabled permanently
Enabled until a new file is opened

[ProgerXP]

On the second thought, rename 2nd to just Enabled permanently

[cshnik]

Done.

[ProgerXP]

when application loses focus - current file is saved, unless it's unnamed (wasn't yet saved).

The purpose is to avoid producing dialogs (interactivity) on deactivation.

[ProgerXP]

What's the purpose of bSkipFirstReset here?

+void n2e_ResetSaveOnLoseFocus()
+{
+  static BOOL bSkipFirstReset = TRUE;
+  if (bSkipFirstReset)
+  {
+    bSkipFirstReset = FALSE;
+    return;
+  }
+  if (iSaveOnLoseFocus == SLF_ENABLED_UNTIL_NEW_FILE)
+  {
+    iSaveOnLoseFocus = SLF_DISABLED;
+  }
+}

[cshnik]

when application loses focus - current file is saved, unless it's unnamed (wasn't yet saved).

The purpose is to avoid producing dialogs (interactivity) on deactivation.

Are there any problems with current implementation of this feature? Please provide details on the cases which are not correctly addressed (if any).

What's the purpose of bSkipFirstReset here?

The point is: n2e_ResetSaveOnLoseFocus() is called only from generic _LoadFile() method which is always used to create new/open existing file. Application's initialization may cause the very first call to _LoadFile() from InitInstance() to reset feature's state loaded from INI. I.e.: it will be impossible to start application with "Save on lose focus" feature set to "Enabled until a new file is opened" because it will be automatically switched to "Disabled" without actual user activity.