FR: Filters added with Context menu should be added locally

[Highvoltage]

I have multiple folder pairs for syncing
When i do a Compare,
in the Overview list i go into a folder pair, and Right click on a folder to "Exclude via filter"
The filter will be added to the Global filters. - Why?

There should be an option to add that filter Locally in the folder pair that i clicked on
It does not make sense to me why it would default to making a global filter?

Thanks
Matt

[Plerry]

Your suggestion makes some sense.

However, I have a few remarks:
1) Adding to the local filter only would make sense if you have already selected to use local filter settings for the left-right pair the right-clicked file or folder belongs to.
2) FFS would need to be able to determine which left-right pair the right-clicked file or folder belongs to. Not impossible, but posing an extra coding challenge.
3) Some files or folders can/will be part of multiple left-right pairs. In those cases the use of a filter is the obvious way to ultimately prevent an overlap between folder pairs. In some cases the obvious way is to achieve that is by using a global filter rule, in other cases it is best to use a local filter rule.
3a) If you have files or folders that are part of multiple left-right pairs, following your suggestion, how is FFS to know which of the multiple left-right pairs you want to apply your local filter rule to.?
3b) What about cases for which it makes more sense to use global filter rules to prevent overlap?

[Highvoltage]

I think the context menu should offer:

"Exclude via Local filter" *
"Exclude via Global filter"

* Where in Local means the pair you actually clicked the file/folder in.

So the user can decide the best case in each scenario

[Plerry]

> ... the pair you actually clicked the file/folder in.

What do you mean?
You don't click a file/folder in a specific pair; you simply click (right-click in this case) a file or folder in the Compare results. That file or folder can be part of multiple left-right pairs (as per my remark 3) above).

[xCSxXenon]

Well, every comparison result MUST be a result of at least one folder pair, so being able to select a filter rule to be added to the local filters should not ever be a technical issue/limitation. The only problem I see is one stemming from user error, as is typical. If a file is part of multiple pairs, it will show up as numerous results in the comparison results. Inevitably, a user will select the wrong one to create a local filter and be confused/mad, if they even catch it at all. Should the existence of a feature depend on whether people will understand it? I don't think so, because there's always a dumber user LOL
Sounds like a good idea to me

[Highvoltage]

"Should the existence of a feature depend on whether people will understand it? I don't think so, because there's always a dumber user "

LOL, as a UX/UI designer i know all too well about this problem :D

As a counter example I for one was confused from the CURRENT behavior. I spent half an hour setting up filters, and all the way through i was CERTAIN it will apply a local rule, since that was my personal "dumb" interpretation. Then it took me a lot of time to actually trace back why my filters not working properly, and what happened to them at all.

So this is one example where the current behaviour might be confusing for a certain individual.
But from this discussion i totally get why it's also a very viable need.

So having both options would be very welcome, and i think it would even make thing CLEARER, since it would function as a visual clue, and make the user think about if they want a Local or a Global filter, and that there is a difference.