I see this wasn't reported as a bug .
This is a big problem when manipulating files back and forth and in particular when the selection list is large and that extra file is not noticed.
A deletion at that point after turning off the filter would delete that "extra" file .
Given the general assumption that selection of a file unselects the prior selection, I find it hard to come up with any reason that justifies this behavior.
Because in my case I am dealing with altered files of the original. After altering, I delete the originals but then eventually rename them back.
At that point I perform one more rename ( admittedly not a delete) but which still affects that extra file.
Regardless of why I do or do not delete or rename or whatever should not be valid reason for considering the behavior of what a regular selection is "supposed" to do or what I think is assumed to do.
It is useful to some people that they can (as one example) filter, select some files, then filter differently, add to the existing selection, then turn off filtering and be left with the combination of those two selections.
If you don't want then it's easy to deselect-all before filtering, or to apply whatever action you want while still filtering instead of turning off the filter before applying the action.
I can only state again that the usefulness of a "bug" for some people is not a valid reason for allowing it to continue given the consequences.
I think it is a long time understanding that "normal" selection of a file automatically unselects the prior selection unless one has taken steps to do otherwise such as with a CTRL.
well, I already have a filter bar which I use which works as a toggle.
Putting in "selecct none" would also turn off my last selection whether I toggle the filter on or off. But I may do that for now even if I have to re-select.
The issue here isn't only how the filter works but the general assumption/default of "what selecting a file" means/does.
Nothing personal , Leo.. but if you are not sure whether it is a bug or not, then I hope the issue is at least escalated for more consideration.
I would not ... but that doesn't change what I expect when I select what I presume is just 1 file.
I think "select all" has always meant to select all items in the lister ... whether it was a filtered one or not. Files not visible in the lister are not, in my view, actually in the lister.
No one would it expect it to select system or hidden files which may have a HIDE attribute.
[quote="hpearce"]
I think it is a long time understanding that "normal" selection of a file automatically unselects the prior selection unless one has taken steps to do otherwise such as with a CTRL.[/quote]
True, but does that long time understanding even involve the concept of filtering?
I'm not agreeing or disagreeing with the way you wish this would behave, but adding an additional concept on top of a long time understanding and then saying that changed behavior of the long time understood behavior is obviously a bug seems a bit strong.
[quote="hpearce"]well, I already have a filter bar which I use which works as a toggle.
Putting in "selecct none" would also turn off my last selection whether I toggle the filter on or off. But I may do that for now even if I have to re-select.[/quote]
How are you toggling the filter bar...? Perhaps you could do something like this (which doesn't actually work, but perhaps can be MADE to work with the right commands):
@ifset: set quickfilter
set quickfilter
@ifset:else
select none
set quickfilter