Visual filter suggestions

[Gandolf]

I keep finding myself doing the same visual filter operation over and over again so, a couple of menu suggestion regarding visual filters:

1. Show everything except the selected extension (or hide the matching extension, whichever you prefer).
2. Toggle between the last two filters used.


1 could be quicker than typing !*.ext if I want to see all files except a particular type.

2 would satisfy my frequent switching between *.jpg & *.html which is common when I'm making up HTML pages with images in them. This may have limited use and obviously requires the need to remember the previous used filter (unless you can find some clever way of indicating the previous filter).

[jacky]

1. Show everything except the selected extension (or hide the matching extension, whichever you prefer).

Yeah, basically the "opposite" of the Filter By Selected Extensions(s), as in instead of ony showing the selected extentions, it would hide them. This could indeed be a nice addition, I think.

2. Toggle between the last two filters used.

Not sure abou this one, but here's a tip if you often need to use the same VF over & over: add them to your Catalog!!
For example, you can add "|*.jpg;*.jpeg" as destination for an item called "JPEG only", and another one "|*.htm;*.html" called "HTML only". That way, all it takes for switching from one VF to the other is one click! (and when CKS will be supported for catalog items, you'll even be able to do it using a KS!)

Last thing, you can even have an item with destination "|" (pipe sign) and call it "No VF". Clicking it will remove any currently set VF.

[admin]

Okay, if any of you gives me a good caption for the opposite/inversion of "Filter By Selected Extension(s)"...

[jacky]

Okay, if any of you gives me a good caption for the opposite/inversion of "Filter By Selected Extension(s)"...

hmm... "Filter All But Selected Extension(s)"

[j_c_hallgren]

Or "Filter By Non-Selected Extensions"?

[Gandolf]

...Not sure abou this one, but here's a tip if you often need to use the same VF over & over: add them to your Catalog!!
For example, you can add "|*.jpg;*.jpeg" as destination for an item called "JPEG only", and another one "|*.htm;*.html" called "HTML only". That way, all it takes for switching from one VF to the other is one click! (and when CKS will be supported for catalog items, you'll even be able to do it using a KS!)

Last thing, you can even have an item with destination "|" (pipe sign) and call it "No VF". Clicking it will remove any currently set VF.

Brilliant. Thank you jacky. I've actually found a good use for the Catalogue! Since I have very few folders I use on a regular basis I've never seen any point in using the catalogue to access them, and I haven't investigated other uses due to lack of time.

I'd still like the "Filter All But Selected Extension(s)" option, but the requirement for Toggling between the last two filters used is not so important now, but still a feature I would find useful.

[admin]

(and when CKS will be supported for catalog items, you'll even be able to do it using a KS!)

I'll make a scriptable hotkey for "Set Visual Filter ...".

[admin]

Or "Filter By Non-Selected Extensions"?

I just added it, but then on a 2nd thought I find these not easily comprehensible:
Filter By Selected Extension(s)
Filter By Non-Selected Extension(s)

Why not simply call them:
"View only Selected File Types."
"Hide Selected File Types."

I know it is slightly incorrect, because
- it can be folders, too, not just files
- type is not exactly the same as extension

But hey, we all know this and the new captions are easier to process for the brain, or?

[j_c_hallgren]

Given that this is being done via a VF, I think keeping the "filter" is needed, so one knows clearly that it is done as such...

The Ext .vs. File Type issue brings up an interesting question: Why does Filter say "Ext" while "Select by Selected Types" have the other?
Do these work the exact same or not? I'm not sure now...

I thought we had a prior discussion about this type or ext verbiage/usage, but where/when?
Update: Yes! Here it is: http://www.xyplorer.com/xyfc/viewtopic.php?t=1184

Also, given that "Filter by Sel Ext" was easily understood, I think, having the "Non-" variant under it makes it quite clear to me that it's the negated one.

[admin]

Also, given that "Filter by Sel Ext" was easily understood, I think, having the "Non-" variant under it makes it quite clear to me that it's the negated one.

It might be my personal problem or something related to German, but for me the expression "filter [by] X" is near-ambiguous. I always have to think twice to understand whether X passes the filter or is filtered out (remains in the filter; does not pass). So I'd like to avoid the word filter and simply talk about the results: show or hide ...

PS: yes, "Select by Selected Types" also works on extensions! So it would be consistent to use "Types" here too.

[jacky]

It might be my personal problem or something related to German, but for me the expression "filter [by] X" is near-ambiguous. I always have to think twice to understand whether X passes the filter or is filtered out (remains in the filter; does not pass). So I'd like to avoid the word filter and simply talk about the results: show or hide ...

Well, I would agree with jc that keeping "Filter" is good, to indicate the relation with VF, and also that since "Filter by Selected Extensions" was working fine for people, using a "Non-" prefix should make sense I think.

If you want something else, how about "Filter Selected Extensions In" and "Filter Selected Extensions Out" ?? Would that make sense?
To me, sounds like filter it in means only "it", while filter it out means everything but "it" ; but I might be wrong here, could jc or any native-speaking English comment on this?

PS: yes, "Select by Selected Types" also works on extensions! So it would be consistent to use "Types" here too.

Hey Don, you didn't read the code when saying that right? Cause I'm pretty sure it does NOT! It's uses "Type" here and "Extensions" for VF because that's exactly how it works !!
"Select by Selected Type(s)" will do just that, it's based on Types and not extension, but since VF can't be based on Types they use extensions, hence the different words used here!

[j_c_hallgren]

To me, "Filter by X" implies that X will pass thru, while "Filter X" implies that X will be trapped...

And in the thread that I linked to, jacky and I seem to agree that File Type is not always specific, while Extension is....
Example: .htm and .html both show as type HTML but I want/need to distinguish between the two on a filter...so by saying Type, it implies both, whereas Extension means either or both, depending on which have been selected, ok?

Update: While I was typing this, got a phone call, so jacky beat me with a reply...which I definitely agree with...as VF deals with EXTensions...

[admin]

PS: yes, "Select by Selected Types" also works on extensions! So it would be consistent to use "Types" here too.

Hey Don, you didn't read the code when saying that right? Cause I'm pretty sure it does NOT! It's uses "Type" here and "Extensions" for VF because that's exactly how it works !!
"Select by Selected Type(s)" will do just that, it's based on Types and not extension, but since VF can't be based on Types they use extensions, hence the different words used here!

YIKES! You're right, of course...

[admin]

To me, "Filter by X" implies that X will pass thru, while "Filter X" implies that X will be trapped...

And in the thread that I linked to, jacky and I seem to agree that File Type is not always specific, while Extension is....
Example: .htm and .html both show as type HTML but I want/need to distinguish between the two on a filter...so by saying Type, it implies both, whereas Extension means either or both, depending on which have been selected, ok?

Update: While I was typing this, got a phone call, so jacky beat me with a reply...which I definitely agree with...as VF deals with EXTensions...

Okay -- I give up.

But wait ... What I actually do with the new function is negate the currently selected extensions, = use an inverted VF, e.g. "!*.txt" -- this is not the same as filtering by non-selected extensions! So "Filter by non-selected extensions" is a misleading caption...

Following your recent English lesson:
"Filter by selected extensions" vs
"Filter selected extensions"
Hm. It might be correct English, but I'm not happy with it. Quite confusing for non English speakers...

[jacky]

Following your recent English lesson:
"Filter by selected extensions" vs
"Filter selected extensions"
Hm. It might be correct English, but I'm not happy with it. Quite confusing for non English speakers...

Assuming that's correct English as well, would "Filter Selected Extensions In/Out" sound less confusing? Since the In/Out specifically indicates whether or not the selected extension will be shown or hidden...
Or "Filter by Selected Extensions" vs "Filter Selected Extensions Out" ?