I put in about 20 notes – no text, just names, and prototyped with a set-type key attribute. I haven’t input anything into any of the sets.
If I make an agent and just enter:
$NameOfTheSet.count==0
I get the spinning wheel and eventually a crash or I have to force quit.
However, If I put in the path to the container the notes are in using “inside”, it seems to work fine. This does limit the agent to that container, however. I’ll do some more testing to see if I can get it searching wider.
7.5.6 running on a pretty wimpy 2014 MacBook Air (4GB ram).
Set up a root-level container called DATA (or something), which will be the parent container for all your substantive notes. That is, the real info in the file, as opposed to the structural or “system” notes – prototypes, templates, plumbing of various sorts.
Move all your containers that include substantive notes into that \DATA container
Then, set all your queries like ($NameOfTheSet.count==0) to look within the \DATA container.
That would give you the functional advantage you’ve uncovered (that a search-within-a-container works better), without limiting the search in any way, since you know that the notes and data you want to search will be inside that container.
Do you still have that test file? Could you post a link to it so others can try the file? So far, I can’t replicate the issue using a variety of Set-type attributes.
It’s almost definitely a memory and/or CPU thing. When I shut down the ridiculous amount of Chrome tabs and other cruft I had running, the agent worked in its simplest form of just $Nameofset.count==0.
I am looking at upgrading my machine at some point soon(ish).