Update Recent Objects and Recent Commands in real time

[skurfer]

There could be a very long delay between the time you use an object and the time it shows up under "Recent Objects". This makes objects available via the catalog entry as soon as they go into Quickilver’s internal history.

I did this for Recent Commands too, but note that this won’t provide much benefit until the commands can be archived correctly.

The QSCatalogEntryInvalidated notification was already defined, but it wasn’t being used. I’m sure there are other places where having this available will prove useful.

[pjrobertson]

Looks good and works as advertised. Merged

Not heard about QSCatalogEntryInvalidated before, but it sounds useful. When I was checking how many times writeCatalog: got called a few days ago, I noticed the QSCatalogSourceInvalidated notif was being sent quite often. Perhaps it should be switched out for the …EntryInvalidated notif in some places?

[skurfer]

Not heard about QSCatalogEntryInvalidated before, but it sounds useful.

Me either. I went to define something like it and saw that it was already there.

When I was checking how many times writeCatalog: got called a few days ago, I noticed the QSCatalogSourceInvalidated notif was being sent quite often. Perhaps it should be switched out for the …EntryInvalidated notif in some places?

Oh, I'm sure. I tried using QSCatalogSourceInvalidated at first, but when I looked into it further, I saw that it triggers an update for every single entry from that object source. I can't imagine why this would ever be appropriate for the filesystem object source (or any of them really), but I think it happens.