https://invent.kde.org/teams/frameworks-devs/kf6-workboard/-/issues/5
utility-macro in KPluginFactory that allows registering multiple plugins? - https://invent.kde.org/teams/frameworks-devs/kf6-workboard/-/issues/ 5#note_446289 - sounds useful, but challenge is variadic macros - macro variants for 2 plugins in one factory would probably already cover most usecases changed plugin/kcm locations: - https://invent.kde.org/teams/frameworks-devs/kf6-workboard/-/issues/ 5#note_446290 - can be done if there are no users loading things manually - location of the plugins is not considered public API use of KWaylandServer::SurfaceInterface* in kwineffect properties - https://invent.kde.org/teams/frameworks-devs/kf6-workboard/-/issues/ 5#note_445378 - Q_DECLARE_OPAQUE_POINTER might help (see also https://www.qt.io/blog/whats-new-in-qmetatype-qvariant) - verify this is even in use QNetworkAccessManager::setNetworkAccessible(QNetworkAccessManager::NotAccessible) - https://invent.kde.org/teams/frameworks-devs/kf6-workboard/-/issues/ 5#note_445360 - only option might be to implement a subclass of QNAM not doing actual network operations - should be testable by modifying the default QML theme and using the screen locker test mode https://codereview.qt-project.org/c/qt/qtbase/+/393373 - ping TQC about this, seems stalled Next meeting in two weeks: https://invent.kde.org/teams/frameworks-devs/kf6-workboard/-/issues/6
signature.asc
Description: This is a digitally signed message part.