Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separation of Exclusionary Rules #72

Open
Raffael7777 opened this issue Aug 10, 2013 · 0 comments
Open

Separation of Exclusionary Rules #72

Raffael7777 opened this issue Aug 10, 2013 · 0 comments

Comments

@Raffael7777
Copy link

Currently the rules function with an ALL/ANY setup. However, from my testing, this also affects the "Exclude files with any(?) of these attributes: -Read Only -Hidden -System".

I was trying to have Belvedere sort a desktop to contain only shortcuts, the recycle bin, and a named folder, sorting anything that was not one of those into the named folder to be sorted.

So the rules looked like this:
"If ALL of the following conditions are met:
-Extension is not lnk
-Name is not Recycle Bin
-Name is not Desktop Autosort
Do the following:
-Move file to folder: Desktop Autosort"

However, on the desktop is a hidden desktop.ini file. Trying to exclude it via name or extension did not work because it was hidden(?). But when I simply checked all of the exclusionary boxes mentioned above (read only, hidden, system) simply to catch it, and any other system files that might later be created on the desktop, it was still getting through the test. This appears to be because it inherited the ALL from the conditions, rather than retaining the "any" stated here: "Exclude files with any of these attributes:". So to exclude the desktop.ini file, I had to only have the hidden check box checked.

The "ALL" from the conditions and the "any" from the exclusions should be separated. It could also be improved, by changing the "any" in the exclusions to another separate "ALL/ANY", for more precise or more broad filtering.

Are you still working on Belvedere, or should I look into making a clone repository and fixing this myself?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant