Nah, I have some buttons that do a sequence that will first deselect whatever is selected, to make sure I don't have to worry about what is selected before using the button.
But when it works it has no way of storing what is currently selected, so it always ends up with everything deselected. Would be nice if it could temp retain the selection.
Maybe I could tell these buttons to use checkbox mode instead. That might work.
I just learned that the 'deselectnomatch' argument actually deselects checkboxes too, even though the term 'select' is in the word 'deselect', which is the opposite of checkboxes but ok.
So I might have to do something like a temp file collection or something. You know, the thing the Find tool is supposed to use.
I'm also thinking some kind of clever way to determine add-to selection or replace selection. Sometimes I might want to add to what I already have selected and my 'deselectnomatch' buttons will break that too, even with checkboxes. Dammit.
This probably could be done with scripting, but will require a little more than a few lines of code.
Depending on what you want to do with the initial selected files, DopStack could be a workaround.
It won't allow for reselection of the files but if you want to copy the files to somewhere else, that should work.
EDIT: Made a tweak to the original DopStack so it allows to reselect from the stack. It's in the last post of the other thread.
I just found there is a 'Reselect' command. It will reselect from a lost previous selection.
That tells me Dopus is keeping track of selections, so we would just need to call it.
Your mention of this 'Dopstack' add in got me to connect the dots and make a cool temp folder thing, kind of like a collection.