Is it possible not to delete non-existing items from collections?
I use collections to have access to most frequently used files in a project but the files are deleted when switching between Git branches. And once they are deleted and recreated, they are no longer in a collection.
v11.18
I don't think there is a way to make it ignore deletions completely.
Depending on how long there is between the deletion and the re-creation, Preferences / Miscellaneous / Advanced: collection_change_delay may help, but I'm guessing that changing branches takes more than a few seconds, and you wouldn't want a huge delay, at least not for for all collections. (And it cannot be set per-collection.)
Using shortcuts or softlinks may be a good alternative to collections here.
Both solutions have downsides. Maybe you can give me some clues how to omit them?
Bat files - I can't select multiple shortcuts to a .bat file, right click and choose "open" - there is no open option when shortcuts are selected.
Symlinks - if I label a symlink, the original file gets labelled. But I'm unable to remove that label (using a shortcut on the symlink).
Yesterday I had files in a collection that got deleted (not directly from the collection view) and these files remained in the collection with a file size of 0 byte. Is that expected behaviour or the exact feature you are looking for, daroc? o) These files were located on a UNC path.
Having a 0-byte collection item for (temporarily) removed file would be ok.
But if a collection item points to a real file on local disk, the collection item gets automatically removed within several seconds.
A script could resolve the links and then run them, but it would be a it of a pain and I'd probably go with symlinks if mass-launching .bat files is something you need to do.
That will be fixed in 12.0.8.
Can this "feature" be supported for local files as well? Having a 0-byte item is okay since it allows you to know which files was moved either by accidentally or intentionally which gives you a chance to update them. It seems like a better way than using the change delay since what happen if you weren't aware of an accidental move while you were sorting files and stuff?
Both approaches have pros and cons, I guess. It would be best to decide per collection whether to delete missing files or to keep them.
Can this "feature" be supported for local files as well? Having a 0-byte item is okay since it allows you to know which files was moved either by accidentally or intentionally which gives you a chance to update them. It seems like a better way than using the change delay since what happen if you weren't aware of an accidental move while you were sorting files and stuff?[/quote]
Could you please re-consider this?