Mr_Noodle wrote:The order of the rules matters in terms of how they will be executed so re-sorting them for cosmetic reasons is not a good idea. Can you describe why you have that many rules?
I use Hazel to import scanned documents for my Paperless Office workflow. I created a rule for frequent bills, statements and other documents based on unique strings found within each document, like account numbers. So I have many copies of the same rule where the only change is the unique string that is searched, and the destination folder in EagleFiler and tags to be added.
If the order of the scripts is important for some people to control the order of execution, it's not for me, at all.
I can imagine a new rule property to manually define the order of execution by assigning an ordinal number. Then allow rules to be sorted alphabetically, but execute according to the execution order, manually defined by that new property.
Or I suppose a global property could be added to allow sorting alphabetically (thus redefining the order of execution). That option would be backwards compatible for folks who don't want to sort rules and rearrange their already set order of rule execution.
If the new global property, "Allow Rule Sorting" was set to true, clicking the column heading would sort the display of the rules alphabetically, otherwise if the property was set to false, clicking the Rules column heading would prompt a message box explaining the feature.
My two cents...
-Dave