Is org.kde.taskmanager intended to be a supported QML API?

Development
1

I had a plasmoid for Plasma 5 that was a virtual desktop indicator/switcher. I’ve been away from Linux for a while for reasons, but upon my return after getting it up to snuff for Plasma 6.0, I found out that in Plasma 6.6 private pager import was no longer working.

Fair enough, I imported org.kde.taskmanager instead and it works great, except that I’m unable to switch the desktop via the plasmoid. Though I can reference read-only properties just fine, it looks like the existing request methods are not Q_INVOKABLE, in particular the requestActivate method.

My intent is to keep this plasmoid pure QML for ease of distribution/end-user installation. Currently I plan to work around it by shelling out to dbus commands, but ideally I’d like to only use org.kde.taskmanager. Is org.kde.taskmanager intended to be a supported QML API for third-party plasmoids? Or is it considered an internal implementation module, despite its public QML import and exported types?

If the intent is for it to be a supported API, I’d be happy to create a merge request for this, but I wanted to be sure of the intent of the module before doing so.

Thanks!

2

org.kde.taskmanager is pretty much internal. requestActivate not being invokable is normal atm

dbus still switches desktops for me:
-qdbus6 org.kde.KWin /KWin org.kde.KWin.setCurrentDesktop N
-or dbus-send --session --dest=org.kde.KWin --type=method_call /KWin org.kde.KWin.nextDesktop

file a wishlist on bugs.kde.org if u want that method exposed for pure qml later

3

Thanks for this. I’m already using dbus so it’s really not an issue, but it would be nice to have a reliable and known API to use. I’ll submit a wishlist entry, thanks for the insight!