Noodlesoft Forums

I was trying to create a simple condition.

If a filename is renamed in the Finder, then apply the rule, "Add Tags" -> [RecentlyRenamed]

So,
Conditions:
- Kind is MOVIE
- Name = Did Change

The Preview says that the second condition failed, even though the file has been renamed.

What have I missed?


(the forum and KB didn't seem to have much on the 'name' condition with the 'did change' option. )

This may not be a good case for "did change" as I believe what is happening is when you change the name, it appears as a new file to Hazel. Try using "Date added is afte Date last matched" and see if that works.

Mr_Noodle wrote:Try using "Date added is afte Date last matched" and see if that works.

Thank you for the reply - are you suggesting that "Date added" is not the Added Date on 'get info' in the finder, but rather the date it was added to Hazel's database?
I guess I may not understand how hazel even detects change in that way

And if Name 'did change' isn't what I thought, then what is it used for? What does the condition meet?

It should line up with the system's date added but note that in Finder, it sometimes fakes the date added and uses date modified instead. If you use Hazel's preview function, you can see what Hazel uses as the date added.

Having "Name did change" is there because "Name" is like other textual attributes and thus shares the same operators (is, is not, starts with, etc.).

Thanks for your continued response. I guess I would like to ask 1 more question, and contribute my findings.

Question: What is the condition "Name" with attribute "Did Change" used for? What is a use case where is would match rule?



Findings: I could not get any data point or date to change when changing a name.

I named a file FilenameTest123.txt on 1.59pm
Then I renamed it in the finder at 2.04pm.
There are no indications at the Hazel Preview that anything has changed, so of course, assuming the the rule doesn't match.

upload images

Based on this, I think I get it... Hazel captures the date of the last time it checked a file and it's basic attributes?

So, I guess, would it make more sense to use Date Last Modified is after Date Last Matched 'because' it uses the last time hazel compared the file in Hazels' database it the file itself?

With that in mind, is there a way that we can see how Hazel sees the file, rather then how the finder does?

The preview/rule status is the best way to see the attributes Hazel sees.

Mr_Noodle wrote:The preview/rule status is the best way to see the attributes Hazel sees.

That's what I thought. I appreciate it. I think the wholistic issue I am seeing is that since Finder/Spotlight doesn't see a 'change' then Hazel isn't either.

Using 'changed since last hazel check' seems to be working for me. I thank you for the feedback on this