On 2022/12/19 20:17, Volker Krause wrote:
From that point on, KDE Frameworks 5 is considered feature-frozen, feature
work should continue to happen in the master branch, primarily targeting KF6
then.
If I merge a merge request now in Frameworks group now, will the change
exist in KF5.102, or KF
Due to my previous mistake in KIO::DropJob, the "Ark drag-and-drop" will
crash plasmashell.
https://invent.kde.org/frameworks/kio/-/commit/5a53a629f0cc6c8836dda37dcde702bd5f37d6ff
Thanks,
Fushan Wen
On 2022/2/13 21:31, Martin Koller wrote:
But still I wonder if such a change is something like breaking ABI
compatibility.
If KDE/plamsa is such a moving target where I can not rely on compatibility even
between minor versions, that is really not fun.
Perhaps the breakage is due to these comm
On 2022/2/13 20:20, Martin Koller wrote:
I already tried this but it did not solve the issue.
This code snippet works on my system. Please have a try.
```cpp
dialog = new KCMultiDialog();
KPluginMetaData
module(QPluginLoader("plasma/kcms/systemsettings/kcm_bluetooth"));
if (!module.name().i
On 2022/2/13 05:46, Martin Koller wrote:
What has changed and how would I now use the new KCM in a KCMultiDialog ?
It can be changed to "kcm_bluetooth". Please see [1] to see if that helps.
[1] https://invent.kde.org/plasma/bluedevil/-/merge_requests/49
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 i
