Axel Dörfler wrote:
So what do we agree on?When using a live query, chances are very high that you want to monitor the file in question, anyway. Since the entry didn't change wrt the query, I would find it cleaner to keep that separated. Introducing B_ENTRY_MOVED would also require userland apps to support this (unlike my previous B_ENTRY_REMOVED/B_ENTRY_ADDED hack).
Whatever works :) Btw i just realised that it isn't exactly a B_ENTRY_MOVED that we need, since it's about any attr/stat change not invalidating the query predicate.
I'm intensively debugging Tracker at the moment, and noticed that it definitely fails bumping the monitor limit at around ~64K. Probably the cause of the bug i was investigating.
Regards, Alex