Retain indexed properties for a short period after files are deleted

[santilli]

This didn't have to be its own topic but I didn't find a suitable existing topic, the thing is I just noticed that every now and then I press the del button by accident and delete folders with hundreds of files... By the time I press CTRL+Z the files' properties are gone already, and it takes a while to repopulate. It would be optimal to retain indexed properties for a short while before they are discarded, just in case they're deleted by accident.

Just a very minor inconvenience

[horst.epp]

This didn't have to be its own topic but I didn't find a suitable existing topic, the thing is I just noticed that every now and then I press the del button by accident and delete folders with hundreds of files... By the time I press CTRL+Z the files' properties are gone already, and it takes a while to repopulate. It would be optimal to retain indexed properties for a short while before they are discarded, just in case they're deleted by accident.

Just a very minor inconvenience

Not a good idea.
There constantly updates to files across the whole system.
It doesn't make sense to set a delay for all files because users will miss any updates in this time.
Not worth the pain for all users just to handle your accidental file deletions.

[santilli]

Not a good idea.
There constantly updates to files across the whole system.
It doesn't make sense to set a delay for all files because users will miss any updates in this time.
Not worth the pain for all users just to handle your accidental file deletions.

shit, this really shouldn't have been a topic... i should have emailed void directly
i'm only reporting a behavior that is not ideal, with the intention of letting it be known to the developer in case he isn't already.

i am talking about indexed properties, which are manually set by the user following their own set of rules. those properties already have a read on change delay by default, which can be tweaked in advanced settings. the purpose is to avoid re-indexing properties that are being changed frequently or in real time, for better performance. it does not affect excluded files though, indexed properties are immediately dropped from the database upon file exclusion.

so to make it crystal clear, the app already allows for the user to set a property retention buffer, the problem is that it does not encompass excluded files, thus rendering the purpose of a property retention buffer innefective.