Giving that the QDBusInterface introspects the DBus interface blockingly in its constructor.
Details
Details
Diff Detail
Diff Detail
- Repository
- R119 Plasma Desktop
- Branch
- app-style-gtk-port-from-qdbus-interface
- Lint
No Linters Available - Unit
No Unit Test Coverage - Build Status
Buildable 21367 Build 21385: arc lint + arc unit
Comment Actions
Why don't you just export the interface you are using through qdbusxml2cpp and viceversa? This way you don't need to have the glue code.
Comment Actions
- This introduces build-time dependency on kde-gtk-config, which should be avoided (because it is also a dependency on GTK).
- The *Interface classes here are very similar to what qdbusxml2cpp generates, except that here they are extracting the value of reply (reply.value()), hiding the QDBus implementation details, and that they make synchronous calls where it is needed.
Comment Actions
Ping! Do I sound reasonable? Any suggestions how can it be simplified without depending on kde-gtk-config?