Exceptions for "Without Saving" Settings.

[SkyFrontier]

Now I really have a good reason to wish that.
Sometimes I wanted to establish a minimum set of exceptions since some changes are not monitored by "Save All Settings" button thus not providing the "green/brown" visual hint.
Now we have this:

Code: Select all

v9.60.0114 - 2010-10-29 11:04
    + Menu Scripting | Run Script: The script is now remembered between
      sessions. Also the wrapped state of the Run Script text box is
      remembered.

...and I'm wondering if List Management could offer another entry to manage which settings would be saved despite all the "exit without saving" settings. Features' captions could be monitored and used as reference on this, for instance?

Code: Select all

List Management > Exceptions (save this on exit)*
+/Run Script... (will keep last executed script without any intervention, while preserving the rest of XY settings intact)
+/Save Tags and Comments
+/Save Tabs (+I'm not aware that there are any way to save only current tabs' state except clicking "save all settings"/"save 'whole' configuration", which may not fit user's intention+)
+/Current Lists' Settings (+minor change that is not displayed by the "Save All Settings Button" which I'd like to be remembered in the event of a non-intentional shutdown+)

*regardless of any other "exit without saving" setting.

Thanks!

[admin]

1) Thanks for the bug report.
2) naaah, overkill

[SkyFrontier]

...if for "bug report" you're telling me that "Run Script" will ignore each and every little setting and will *ALWAYS* save the content for the next session I'm more than happy, Don.
That way "Run Script Again" has an extra gain regarding usage, plus making more sense as a test camp/scripting place/permanent CKS for a temporary script (session-driven, which sometimes can take an hour, sometimes requiring whole days and several system restarts/unpredictable shutdown events in the meantime).
So... a huge THANK YOU for that!

[admin]

...if for "bug report" you're telling me that "Run Script" will ignore each and every little setting and will *ALWAYS* save the content for the next session I'm more than happy, Don.
That way "Run Script Again" has an extra gain regarding usage, plus making more sense as a test camp/scripting place/permanent CKS for a temporary script (session-driven, which sometimes can take an hour, sometimes requiring whole days and several system restarts/unpredictable shutdown events in the meantime).
So... a huge THANK YOU for that!

I meant that changes in the "run script" will make settings "dirty" (TB icon turns brown).

[SkyFrontier]

I meant that changes in the "run script" will make settings "dirty" (TB icon turns brown).

It's a gain, for sure.
But this also implies that if I'm testing a script on a folder/file, that state will be save along with the "Run Script" entry and will reflect on my tabs setup on the next restart, perhaps other changes occurred in the meantime, right? This is exactly what I'm trying to avoid...

[SkyFrontier]

If I exit without saving but I have don't save history unchecked that means I could have history saved despite the first condition. Otherwise, it was just a mere fact of checking "don't save history".
What about this?