That way we can use signals/slots with it, e.g. emit a signal upon changes in the
style.
qtui.h
qtuiapplication.h
qtuimessageprocessor.h
+ qtuistyle.h
settingsdlg.h
settingspagedlg.h
simplenetworkeditor.h
chatlinemodelitem.h
chatviewsettings.h
qtuisettings.h
- qtuistyle.h
webpreviewitem.h)
set(FORMS
#include "qtuistyle.h"
#include "qtuisettings.h"
-QtUiStyle::QtUiStyle() : UiStyle() {
+QtUiStyle::QtUiStyle(QObject *parent) : UiStyle(parent) {
}
#include "uistyle.h"
class QtUiStyle : public UiStyle {
+ Q_OBJECT
public:
- QtUiStyle();
+ QtUiStyle(QObject *parent = 0);
virtual ~QtUiStyle();
virtual inline qreal firstColumnSeparator() const { return 6; }
settingspage.h
tabcompleter.h
toolbaractionprovider.h
+ uistyle.h
)
set(HEADERS
icon.h
qssparser.h
uisettings.h
- uistyle.h
)
if(HAVE_KDE)
QHash<QString, UiStyle::FormatType> UiStyle::_formatCodes;
-UiStyle::UiStyle() {
+UiStyle::UiStyle(QObject *parent) : QObject(parent) {
// register FormatList if that hasn't happened yet
// FIXME I don't think this actually avoids double registration... then again... does it hurt?
if(QVariant::nameToType("UiStyle::FormatList") == QVariant::Invalid) {
#include "message.h"
#include "settings.h"
-class UiStyle {
- Q_DECLARE_TR_FUNCTIONS(UiStyle)
+class UiStyle : public QObject{
+ Q_OBJECT
public:
- UiStyle();
+ UiStyle(QObject *parent = 0);
virtual ~UiStyle();
typedef QList<QPair<quint16, quint32> > FormatList;