So I was about to buy fences, but I figured I'd go ahead and try the trial, and I had enough trouble doing what I'm about to detail that I just had to post here. So this is either going to be a bit of a critique, or it's going to result in someone going "You are the biggest dummy head I have ever seen, this is how you should actually be doing that". I am genuinely hoping for the latter because I'd like this program to be viable for me.
So I installed Fences and let it slap together the few default fences. Looks nice. I decide I could use a fence for images and music & video so I make them and then open up the menu to configure it. Under sorting and organizing I see that the first entry is "All new icons go to the general desktop". This genuinely confused me for a moment but after noticing the use of "icon" throughout this section I realized that this software uses "icon" as the name for a file on the desktop as opposed to just "file". I actually really dislike this, but whatever. Anyway I then link up the default rules "Program Shortcuts", "Folders", "Documents", "Music & Video", and "Images" to their respective fences. I hit apply rules now and see that it sorted all but one of the images on my desktop. I notice the image is a .webp file and after a bit of clicking around I edit the rule for Images and add ", webp" to include it. Pretty easy.
Then I decide It'd be nice to have .c files go into a fence called programming. I've been learning C and it's easy to save little source code files on my desktop. Some super basic organization via fences would be nice. So after making my new fence I click "Send certain file types to different places" (I like that it doesn't say "icon types", it's inconsistent with everything else though) and make my rule "The icon's type / is / c". I hit okay and now have a rule titled "Icons whose type is 'c'". I assign it to a fence and it doesn't work, .c files get thrown into the default fence titled "Files and Documents". Soon I find that after hitting okay it's actually saving the rule as "The icon's type / is / Compressed file". So c is being changed to compressed file and the automatically named rule doesn't even reflect that. After adding a comma after c it saves properly.. but still doesn't work. At this point I think to myself, "Okay, I guess they have some extensions such as .c included in the default "Documents" rule, which is the only rule that is putting anything into the default fence called "Files and Documents", that will be really easy to remove, just as easy as me adding webp to images earlier." Well there is no c extension in that rule. But get this.. If you take out every extension in that rule that simply contains the letter c, then that rule no longer gets in the way of my rule ..but now the default music rule does. ..and if you take out every extension in the music rule that contains the letter c, then you now have no problems.
Obviously that's not viable and I didn't keep it that way. I found two better solutions, neither ideal. My first one was to use the rule order setting. I have two issues with this, the first one being that 1: I don't actually know what order the rules in this list are executing in - if I had to guess I would say they are executing in top to bottom order, which would cause rules on the bottom to overwrite ones on the top. But some programs would execute the rules from bottom to top, so you would say that the top rules have "precedence", they would overwrite the ones below them. Now problem 2: is that I technically don't know how this works regardless of which order the rules are executed. Perhaps once a rule places a file into a fence, a later executed rule won't move this file even if the file fits into this rule. ..I just don't know. Regardless of how it actually works, I found that if I moved my c rule to the top of the list that solved the problem. I don't see why I should have to mess with the rule order for a filetype that has no other rules that should conflict with it, but whatever (Actually I do see why, it seems that the rules here are very relevant because somehow the default Documents and Music & Videos rules are including the c filetype when they have a filetype extension containing the letter c in their list.)
The other way I found to fix the issue was to add a second criteria to the Documents and Music & Videos rules, stating that "The icon's type / is not / c,". You cannot however do this to the default rules, so you have to uncheck them, and make your own by copying the filetypes they cover. This is dumb and you would have to edit these rules any time you want to add a new filetype rule that gives you trouble, so re-ordering the rules is likely the better option.
So am I doing something majorly wrong or is this something that might should be worked on?