No launching while the catalog is being updated

[egabrum]

I can't seem to be able to launch anything while KP is refreshing the catalog, which in my case takes a few minutes. It does seem to grant my latest request, but only after it finishes refreshing the catalog.

Together with issue #22, this pretty much makes my KP a sitting duck when I launch it

[polyvertex]

It's in my todo list since ages.

I does seem to grant my last request, but only after it finishes refreshing the catalog.

Which one? #22?

[egabrum]

What I meant to say is:
If, while KP is refreshing the catalog, I try to launch a couple of programs from KP's launch box, it won't do anything.
Once the catalog refresh is completed, KP will launch only the last program that I commanded to open, not the other ones that I tried during the refresh.

[egabrum]

I don't know how much of a problem this is across the user base but, at least for me, it is a major inconvenience:
After logging in (the moment when normally you need the launcher the most), Keypirinha rebuilds the entire catalogue and won't allow me to open anything until it's done cataloguing.
Same occurs every time I undock/dock my laptop (PATH changed).

My catalogue takes a bunch of minutes to rebuild, which renders the tool unpractical for me.

I say this only for feedback, not cynically at all, but this issue, together with #16 (#32) are the only ones that are keeping me from transitioning from Launchy to Keypirinha. I know the day will come, I'm just sharing what the trigger will be for me.

[polyvertex]

The day will come indeed. Feature requests #22, #52 (this one) and #60 are likely to be implemented altogether since they're all related to the Catalog machinery.
I assume you meant to reference #24 instead of #16 and #32.

[polyvertex]

@egabrum I'm marking this as "done" because this issue, at least the way I understood it, should mechanically be solved by the implementation of a persistent catalog mechanism, which will be available in the next release (#22). Your items will be available and searchable at startup time while plugins fetch their items. Once they're done, the list of new items is then merged into the catalog.

Now this "merge" operation becomes the true bottleneck here because catalog is not searchable while being updated (it doesn't duplicate itself to avoid increasing too much memory usage). However it takes only from a few milliseconds up to a second to be done, depending on the size of the catalog and the speed of the CPU.

It's insignificant in most cases but if you still happen to use Keypirinha and experience annoyance after upgrading to next release, do not hesitate to comment here.

[polyvertex]

Should now be obsoleted by the persistent catalog feature implement in v2.10 (see #22).