views:

63

answers:

1

Hi,

I made a prototype of a project with PyQt and made it work there, now I'm trying to convert it to C++ and am having some problems.

If I don't put the Q_OBJECT macro in, it compiles and works, but if I comment it out, I get the following errors:

Undefined symbols:
  "vtable for MapView", referenced from:
      MapView::~MapView()in mapview.o
      MapView::~MapView()in mapview.o
      MapView::MapView(QObject*)in mapview.o
      MapView::MapView()in mapview.o
  "MapView::staticMetaObject", referenced from:
      MapView::MapView(QObject*)in mapview.o
      MapView::MapView()in mapview.o

Here's the header:

#ifndef MAPVIEW_H
#define MAPVIEW_H

#include <QtGui>
#include <QObject>

class MapView : public QGraphicsScene
{
    //Q_OBJECT

public:
    MapView();
    explicit MapView(QObject *parent = 0);
    QGraphicsPixmapItem *mappixmap;
    ~MapView();

private:
    bool dragging;
    float offsetX, offsetY, downoffsetX, downoffsetY;

protected:
    void mousePressEvent(QGraphicsSceneMouseEvent *event);
    void mouseMoveEvent(QGraphicsSceneMouseEvent *event);
    void mouseReleaseEvent(QGraphicsSceneMouseEvent *event);

};

#endif // MAPVIEW_H

Secondary question is will Bad Things happen if I just omit the Q_OBJECT macro here?

And yes, I'm aware of that it's stupid to call a QGraphicsScene a "view".

+2  A: 

This kind of errors usually happen when you add the Q_OBJECT macro and forget to rerun moc. If you use qmake, just run make qmake after you added the macro.

As for your second question: you won't be able to use signals/slots (among other things) without the Q_OBJECT macro. See the docs for more information about this.

Job
Thanks, rerunning qmake indeed this fix this! I don't really need to use signal and slots here, just receive calls to the event handlers I've defined. But I still want to do things the proper way.
teukkam
@teukkam, If your classes are inherited from `QObject`, you will need `Q_OBJECT` macro...
liaK
@liaK: No, you only need it for signals/slots and some other things. See the link in my answer.
Job
Obviously I don't need that macro, because the program works as expected even if I omit it. I just like to have it there so the code looks like how one would expect it to look in the typical case.
teukkam
@ Job, http://doc.trolltech.com/4.6/metaobjects.html Check out this link.. From the docs, **we strongly recommend that all subclasses of QObject use the Q_OBJECT macro regardless of whether or not they actually use signals, slots, and properties.**
liaK
@liaK: I agree it's best practice to use the macro. I just meant it is not strictly necessary.
Job
@ Job, Yeah true.. :)
liaK