If a filter is active for a panel, TC shows an icon underneath the panel to indicate that the content of the panel is filtered. You can click on it to show the filter text box.
If you have to explain someone that something is visible in this state because he hasn't noticed it before, than the current solution might not be optimal. Here is a related thread woth some ideas. I fear we have found the usability issues relaed to the filter but not a solution which is better in all aspects.
You can press Ctrl+Shift+S to open quick search with the last used search string. I don't know whether it works also with Quick Search Extended, please try it.
Thanks for the button tip. Thanks also for the shortcut tip.
First, there are shortcuts which one remembers better and ones (particularly application-specific or even plugin-specific) which do not memorise so well. Ctrl+Shift+S is among the latter. Yes, of course I can change it to something more convenient but that means additional configuring.
Second, there is also the question how to quickly open Quick Filter (or QuickSearch Extended) when I want to copy-paste a filter string into it. Suppose I have selected some text elsewhere and want to quickly paste it into the filter. I first have to activate the filter with Ctrl+S and only then I can paste (Ctrl+V). It works and I have done it for some years now but somehow it still feels a bit awkward.
Third, if I want to apply the same pasted filter string in multiple different directories consecutively, I will have to either reopen the filter (Ctrl+S) and repaste the string (Ctrl+V) after every change of directory or use Ctrl+Shift+S (which replaces Ctrl+S plus Ctrl+V) but the latter is one more shortcut to be memorised. Again it works but feels a bit awkward (in particular because sometimes I do not remember exactly what was the last filter string I used).
Fourth, the button indeed shows that there is some kind of a filter string applied but in order to see the filter string, I have to perform an additional click on the button or an additional Ctrl+S. But with some tasks it is good to have the filter string visible all the time.
Having a filter box visible all the time (as an option) just seemed a good idea to me.
Third, if I want to apply the same pasted filter string in multiple different directories consecutively, I will have to either reopen the filter (Ctrl+S) and repaste the string (Ctrl+V) after every change of directory or use Ctrl+Shift+S (which replaces Ctrl+S plus Ctrl+V) but the latter is one more shortcut to be memorised. Again it works but feels a bit awkward (in particular because sometimes I do not remember exactly what was the last filter string I used).
I guess in this case you might want to use a permanent filter (Ctrl+F12).
Maybe there is a way to combine this two kind of filters somehow? Anything that reduces complexity is welcome. The permanent filter is already visible all the time - as part of the path.
I also read the other thread. In my opinion, the simplest yet elegant solution would be an optional small box not in the path area of the Current Directory bar but in the same bar separately (towards the right).
Ideally, the width of the box and the font used in it would be configurable. Perhaps more options, as are now offered by Quick Filter and/or Quick Search Extended.
Having the filter string directly in the path area (as shown e.g. by nsp in the other thread) would somehow confuse the concept of path as such.
2andres992
As this is exactly my original idea you may have read the arguments from others against it. Although I don't agree with most of them I have to admit that the path really needs the space - which is also an argument against the way ther static filter is displayed BTW.
If a filter is active for a panel, TC shows an icon underneath the panel to indicate that the content of the panel is filtered. You can click on it to show the filter text box.
If you have to explain someone that something is visible in this state because he hasn't noticed it before, than the current solution might not be optimal. Here is a related thread woth some ideas. I fear we have found the usability issues relaed to the filter but not a solution which is better in all aspects.
By this very broad argument most UI-related features ever made for any software are not optimal, because there will always someone in the wide world which did not notice something because it did not cover at least a quarter of the available screen estate. Not noticing a thing can happen... Unless many are overlooking or not noticing things, this is not a criteria whether a feature is implemented well in terms of UX.
However, with the example mock-ups posted there in the thread you linked, i agree that the suggestion of you and others definitely is an improvement. Especially the (red) signal color with sufficient "surface area" helps keeping the user aware that the filter is active without distracting the user from whatever tasks (s)he wants to do...
By this very broad argument most UI-related features ever made for any software are not optimal, because there will always someone in the wide world which did not notice something because it did not cover at least a quarter of the available screen estate. Wink Not noticing a thing can happen... Unless many are overlooking or not noticing things, this is not a criteria whether a feature is implemented well in terms of UX.
Define many? Summative testing isn't usually performed for this type of question. For a formative testing you usually hire 8-15 people for each user group. It's proven that more people don't help at all.
However, with the example mock-ups posted there in the thread you linked, i agree that the suggestion of you and others definitely is an improvement. Especially the (red) signal color with sufficient "surface area" helps keeping the user aware that the filter is active without distracting the user from whatever tasks (s)he wants to do...
Yes I think a visual enhancement would be a (small) step forward.
Not noticing a thing can happen... Unless many are overlooking or not noticing things, this is not a criteria whether a feature is implemented well in terms of UX.