When exposing some code to D-Bus using Qt D-Bus bindings, when should one use a Qt Adaptor over a Qt Interface? I’m having a difficult time understanding how exactly they differ since it seems like they provide the same functionality.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When exposing some code to D-Bus using Qt D-Bus bindings, when should one use a Qt Adaptor over a Qt Interface? I’m having a difficult time understanding how exactly they differ since it seems like they provide the same functionality.
Per http://doc.trolltech.com/4.3/qdbusabstractinterface.html, “QDBusAbstractInterface class is the base class for all D-Bus interfaces in the QtDBus binding”, while, per http://doc.trolltech.com/4.3/qdbusabstractadaptor.html, “QDBusAbstractAdaptor class is the starting point for all objects intending to provide interfaces to the external world using D-Bus”. So, the former is used in the interface itself, the latter is used to provide the interface, i.e., for “exposing some code to D-Bus” you’d write a class inheriting the adaptor and “define the D-Bus interface it is implementing using the Q_CLASSINFO macro in the class definition” (also a quote from the second of the above URLs).