Saving settings in event of a crash

[ivan]

Agreed! My terminology maybe wasn't the ideal as what I meant by auto vs auto-save was the saving when changed vs saving every x interval.

Now that we understand each other, what do you think about XY having "saving when changed" feature? Surely, overwhelming number of apps that apply (pun very much intended!) such logic must mean that it should receive serious consideration in terms of being implemented.

[j_c_hallgren]

Now that we understand each other, what do you think about XY having "saving when changed" feature?

As a very low priority item, maybe...but in the interim, I think the possibility of having OnEvent scripting may help.

[serendipity]

Based on a hint by TheQwerty yesterday, I tried the below script for fun. So far nothing bad happened to me, but I have my XY backed up.

Code: Select all

"Autosave : autosave"
   //Save all settings
   #182;
   wait (300000);
 sub autosave

Click on it once and this will auto-save all setting every 5 minutes. To stop it I guess you will have to restart XY. Also, escape will end it. So not very useful if you use too much escape.
Warning: If your XY crashes dont blame me.

[ivan]

Thank you serendipity Though still curious why "save when changed" as opposed to auto-save wasn't part of XY right from the start...

[j_c_hallgren]

Though still curious why "save when changed" as opposed to auto-save wasn't part of XY right from the start...

As we've tried to tell you a few times in this and other threads: Some things are just based on the way Don wanted/wants or his choice of design/method, and we understand that...you just need to know when to accept it and when to try and change it...and this type of persistance isn't always condusive to getting your desired results, ok?

I slowly worked on one issue for over a year, so sometimes it takes a while.

[ivan]

As we've tried to tell you a few times in this and other threads: Some things are just based on the way Don wanted/wants or his choice of design/method, and we understand that...you just need to know when to accept it and when to try and change it...and this type of persistance isn't always condusive to getting your desired results, ok?

I understand. Don't get me wrong, I am not trying to rebel here and I respect the way he does things. Also being used to something that most would consider a common practice does make adjustment that much more difficult.

[serendipity]

Based on a hint by TheQwerty yesterday, I tried the below script for fun. So far nothing bad happened to me, but I have my XY backed up.

Code: Select all

"Autosave : autosave"
   //Save all settings
   #182;
   wait (300000);
 sub autosave

Click on it once and this will auto-save all setting every 5 minutes. To stop it I guess you will have to restart XY. Also, escape will end it. So not very useful if you use too much escape.
Warning: If your XY crashes dont blame me.

OK, I don't recommend this anymore, it's giving some errors because of accumulating stacks I guess. So like always save settings manually if you think you made a major change. Sorry if this script hurt you.

[admin]

Based on a hint by TheQwerty yesterday, I tried the below script for fun. So far nothing bad happened to me, but I have my XY backed up.

Code: Select all

"Autosave : autosave"
   //Save all settings
   #182;
   wait (300000);
 sub autosave

Click on it once and this will auto-save all setting every 5 minutes. To stop it I guess you will have to restart XY. Also, escape will end it. So not very useful if you use too much escape.
Warning: If your XY crashes dont blame me.

OK, I don't recommend this anymore, it's giving some errors because of accumulating stacks I guess. So like always save settings manually if you think you made a major change. Sorry if this script hurt you.

Actually this script let me discover a new bug. So it was worth something!

[admin]

BTW, I think RalphM has said everything there is to say about and against auto-save.

[serendipity]

Based on a hint by TheQwerty yesterday, I tried the below script for fun. So far nothing bad happened to me, but I have my XY backed up.

Code: Select all

"Autosave : autosave"
   //Save all settings
   #182;
   wait (300000);
 sub autosave

Click on it once and this will auto-save all setting every 5 minutes. To stop it I guess you will have to restart XY. Also, escape will end it. So not very useful if you use too much escape.
Warning: If your XY crashes dont blame me.

OK, I don't recommend this anymore, it's giving some errors because of accumulating stacks I guess. So like always save settings manually if you think you made a major change. Sorry if this script hurt you.

Actually this script let me discover a new bug. So it was worth something!

Glad this non-sense script caught atleast a bug.

[ivan]

BTW, I think RalphM has said everything there is to say about and against auto-save.

Well, if "save as applied" would see the light of day then possibility of auto-save would be redundant.

[tnshibu]

It is better if it does not autosave.
what if the crash was because of the changes you made. if they get auto-saved, XYplorer would crash every time it starts up.
I do not think that is what a user would want, unless there is a "start in safe mode"

[ivan]

It is better if it does not autosave.
what if the crash was because of the changes you made. if they get auto-saved, XYplorer would crash every time it starts up.
I do not think that is what a user would want, unless there is a "start in safe mode"

In order for settings to cause a crash they need to be saved so if a crash happens then it doesn't really matter because settings are saved already. I also think that if a person wants to "try" a setting to see how it works then he/she would most likely still have "Save settings on exit" ticked and if a setting doesn't work as expected then he/she will just untick the box. In fact, I'd bet that most people who use XY have the tickbox about saving on exit ticked, so whether on exit or through a crash it wouldn't make a difference to those people how they are saved.

[kartal]

It is better if it does not autosave.
what if the crash was because of the changes you made. if they get auto-saved, XYplorer would crash every time it starts up.
I do not think that is what a user would want, unless there is a "start in safe mode"

That can always happen without autosave feature as well regardless of when or how it is saved. Your config file may get corrupted during a normal exit either. I just think that this logic does not hold much strength really.

There should be a "last known good configuration" startup method for cases like this. Operating systems provide this happily.

Also this whole argument about being anti or pro autosave does not make sense because all is needed is an option in the menu that says "config autosave", after that it is on the user`s responsiblity. Then everyone will be happy, if you hate autosave make sure it is unchecked. There is no need to be snobby about these issues. If the users want such thing then the developers should take a note about it instead of revealing negative sentiments. As a user I come here to ask for help, give my opinion on features. And I personally hate to get a respond like "stop wasting my time". That is just bad response.

[mwb1100]

Not to mention, XY has a "start in safe mode" option already.- rename the problem .ini file. Also, you can get something similar to a "last known good' config by backing up a good configuration file.