XYplorer Beta Club

Scenario:
- Enable auto-saving settings each 30 minutes.
- At any time, tag any file.
- 5 hours later, kill XYplorer process.
- Run it again.
- The file appear not tagged anymore.

My PC crashes once in a month for different reasons, and each time I'm losing some tags. I hope this will be fixed at some point.
Thanks.

· Tagging an item.

· OK-ing the Configuration dialog.

These two seem to be buggy atm (folder changing leads to an instant save...)

Can't confirm any issues. All works as advertised:

Note that Autosave will not happen just by itself but is triggered by the following user actions if the specified number of minutes has passed in this moment:

· Changing location (you browse to some new folder).

· Tagging an item.

· OK-ing the Configuration dialog.

Not here

v18.50.0200, fresh instance

Configuration | General | Startup & Exit | [x] Autosave settings after this many minutes
Set to 1 minute

File - Save Settings

Now I tag a random file with "abc"

3 minutes later: Still no saved settings...

It happens when you tag an item 3 minutes after the last save.

In other words: All (tag) changes that happen during the used period are unprotected
before the period has reached it's end (and XY / OS crashes) until something happens
afterwards (config dialog OK, tagging, folder change).

That's not really what a user expects for an "autosave settings" feature...

Yep, it's semi-auto. The feature is 2 years old and nobody yet complained.

This thread has helped me determine why at times my tags/comments haven't been saved.
I don't use auto-save every X minutes. Different reasons why. But at times I do exit without saving. There's why they haven't been saved.
I assumed whenever I added a tag/comment it auto-saved whenever I clicked OK after adding one or the other.
So I have just added #195 (save tags) to a button. Now I just need to train myself to click it after adding a tag/comment.

Don, any possibility of including a #195 command to the code after adding or editing a tag/comment so it is auto-saved? My thoughts are if someone is modifying one of these two columns it is something they do not plan on being temporary.

kodyman wrote:Don, any possibility of including a #195 command to the code after adding or editing a tag/comment so it is auto-saved? My thoughts are if someone is modifying one of these two columns it is something they do not plan on being temporary.

Unless you make a mistake. Which is the reason why I don't offer full autosave. If you by a slip of the finger destroy anything and it's saved right away to disk, it's gone, bye-bye.

Unless you make a mistake. Which is the reason why I don't offer full autosave. If you by a slip of the finger destroy anything and it's saved right away to disk, it's gone, bye-bye.

Makes sense.
I was only considering adding items. Not the possibility of an "OOPS I didn't want to delete those."
I'll just need to remember to hit my #195 button or exit with saving.

Thanks!

Do you mean that you are not going to fix this issue?
Because users may lose data if they make a mistake? Is it more important to consider than losing data due to crash?
Also, really I agree - if user adds a tag to an item that was not tagged before or changes an existing tag, he should expect to not lose it. Removing the tag is the only case where user may expect losing important information due to mistake.

Sounds like a wish for an option how to save tags, saying:
- as is now
- immediately after create
- immed after change (incl. create)
- immed after delete (incl. change+create)

By the way, to the risk: what happens, if a user deletes a (group of) file(s) by accident? Shouldn't/couldn't the same be possible after delete (or change) of tags for a (group of) file(s)?

I have a feeling this question will return forever if I don't stop it. So I will add this ("immediate save to disk") as an option.