Why does KRunner start loading plugins only after typing for the first time?
Kai Uwe Broulik
kde at privat.broulik.de
Fri Nov 26 16:34:31 GMT 2021
Hi,
when KRunner starts fresh, it will either have to load the plug-ins
right away or when you first type. Either way won't give you the results
any faster, would it? If any, it would delay the KRunner window itself
appearing, making it even more likely your input would not go into KRunner.
If you're looking for a way to optimize KRunner I suggest you
investigate how to make KRunner not wait for the StrutManager in
Plasmashell (plasma-workspace/krunner/view.cpp) to reply before showing
the main window :)
Cheers
Kai uwe
Am 26.11.21 um 17:02 schrieb Fusion Future:
> When I was debugging WebshortcutRunner::WebshortcutRunner, I noticed
> that KPluginFactory::instantiatePlugin (or other functions that load
> plugins) was called after typing for the first time, which makes
> KRunner not able to instantly take input.
>
> Is there any reason not to preload plugins?
>
> Thanks in advance.
>
More information about the Kde-frameworks-devel
mailing list