Here’s an odd one. Certainly not critical, but puzzling.
I was playing around in a test tbx with DEVONthink integration. I am watching a Dt group and it is behaving as expected with the notes at the first group level appearing in the tbx as read-only in the DEVONthink container note. Just for grins I manually created a note in that container along with the watched ones. I was surprised when the NameStrike attribute turned on at the next action cycle. If I turn it off, it will turn on again. If I move the note out of the container and turn it off it stays off. If I move the note back into the container, the NameStrike attribute turns on again. So this action seems to be a property of the watched container. There are no “onAdd”, agents, edicts, or rules associated with the container. Is this some sort of intrinsic property of watched items?
This makes sense as you’re adding a note that doesn’t exist at the DEVONthink end. Recall you are using a watched folder. IOW, Tinderbox is showing the ‘notes’ at the nominated DEVONthink source context. If you add a note at the Tinderbox end, it detects a missing note and indicates that the source note does not exist/is unavailable.
Tinderbox is not expecting a user to deliberately mis-use a watched folder this way but copes well. Bear in mind a watched folder is intended to generate links to reflect the source. as such it controls the in-Tinderbox container and manages it accordingly, for instance generating the strike-though to indicate the missing/broken source given that the only expected items are generated from the data at the DEVONthink end of the watch link.
Tinderbox is saying, “Hey! There’s a note ELMER in this watch folder, so there ought to be a corresponding DEVONthink item. But there isn’t one. Maybe you deleted it?”
We don’t delete the note because, even if you didn’t want it in DEVONthink, perhaps you do want it in Tinderbox.
Thanks. I thought it was something like that. So this is a property of any watched container. I don’t recall seeing it documented anywhere, but it’s not something that would leap off the page is it?
When watching a folder in Finder, notes that correspond to deleted (or moved) files are now shown with their names struck through by automatically setting $NameStrike to true.
Watched folders of all kinds are checked more frequently.
When a file in a watched folder is checked, its $LastFetched is now updated even if the note is unchanged. The note’s $NotesModified attribute continues to reflect the modification date of the file.
Notes in watched folders should update to reflect changes in the remote document, even if $ReadOnly remains set.
Watched folders update documents if they have been modified since they were previously fetched.
From v10.0.0, when watching or importing a folder, the names of imported notes are derived from the file name after removing the extension. For example, the file ‘garden.md’ is imported to a note named ‘garden’.
@eastgate does the above also hold true for watched Groups (a DEVONthink only feature)? If so, I’ll repeat the guidance in the article Watched Groups.
