DBusLogout gets an ApplicationManager pointer just to make a signal/slot connection between the two!?
That's bad design. You're unnecessarily adding a circular dependency between DBusLogout and ApplicationManager. Just make ApplicationManager code create such connection.
Actually I'm not even sure this should be in unity-mir in the first place. As there's nothing "mir" about it.
144 +DBusLogout: :DBusLogout( ApplicationMana ger *parent) : QObject(parent) ::sessionBus( ); nager = parent; :connect( this, &DBusLogout: :LogoutReady, ager::onLogoutR eady);
145 +{
146 + QDBusConnection connection = QDBusConnection
147 + m_applicationMa
148 +
149 + QObject:
150 + parent, &ApplicationMan
DBusLogout gets an ApplicationManager pointer just to make a signal/slot connection between the two!?
That's bad design. You're unnecessarily adding a circular dependency between DBusLogout and ApplicationManager. Just make ApplicationManager code create such connection.
Actually I'm not even sure this should be in unity-mir in the first place. As there's nothing "mir" about it.