That is not what I'm saying at all.
What I'm saying is that Default actions should never be performed if there is an existing rule that has ANYTHING to do with the file being analyzed for actions to be taken against it.
If there is a rule that says that if the subject file contains Steam:// as its target if its a shortcut, then that specific rule COMPLETELY overrides whatever Default has to say. If that file is not recognized as a Steam shortcut, then that shortcut or file needs to end up in New Files WHEN and only when its something NEW presented to Fences based on the Default rule. Given that there are no other rules that affect a file that Fences is already aware of, I'm free to move that file from New Stuff to any other fence I want. If I move a Steam shortcut and it's not new to Fences, the rules I currently have applied ensures that shortcut is to stay WITHIN that Steam Stuff fence.
Lets stick with the assumption that I'm leaving the "Always apply the rules" as being enabled, and lets change things a slight bit as well with a different example. Lets say there are only two rules. Forget my Steam rule, forget the Default rule for now.
- All files older than 30 days belong in the Old Stuff fence.
- All PDFs belong in the PDF Stuff fence
Given this, ALL files that end up on my desktop view are subject to some kind of action. If a file is +30 days old, something is going to happen. If a filetype is a PDF, something is going to happen.
Given these two rules, the PDF is going to end up in one of three places.
- Directly on my desktop
- In the Old Stuff fence
- In the PDF Stuff fence.
If the file is not a PDF, and the file is less than 31 days old, then it'll end up on my desktop.
If the file is a PDF and is less than 31 days, then it'll end up in the PDF Stuff fence
If the file is not a PDF, and is greater than 30 days old, it'll end up in the Old Stuff fence
If the file is a PDF and is older than 30 days then... ... CONFLICT
This is where the order of operations come in, and this is where I think the confusion in understanding between us is coming from. I know that this kind of situation can come up if you have things setup incorrectly. I get it. Fully understood. That's not what my original post is about. It's about Default actions being applied when rules are already defined to handle that file. If I'm having a bad day and make a conflicting rule that is not Default, that's on me, and that's where I have to look at the order of the rules that they're being applied.