Any time you add a new call to the Q_OBJECT macro, you need to run qmake again. The vtables issue you’re referring to is directly related to that.
Just run qmake and you should be good to go assuming there are no other issues in your code.
More Related Contents:
- Q_OBJECT throwing ‘undefined reference to vtable’ error [duplicate]
- Undefined symbols “vtable for …” and “typeinfo for…”?
- When should Q_OBJECT be used?
- Adding external library into Qt Creator project
- Application failed to start because it could not find or load the QT platform plugin “windows”
- How to build Qt for Visual Studio 2010
- Non-blocking worker – interrupt file copy
- How to redirect qDebug, qWarning, qCritical etc output?
- Qt: can’t find -lGL error
- cv::Mat to QImage and back
- Error LNK1104: cannot open file ‘Debug\MyProjectLib.lib’
- QGraphicsView Zooming in and out under mouse position using mouse wheel
- How do I add a background image to the QMainWindow?
- Why is important to include “.moc” file at end of a Qt Source code file?
- what does __declspec(dllimport) really mean?
- How do I create a simple Qt console application in C++?
- Beyond Stack Sampling: C++ Profilers
- At what point is it worth using a database?
- Using pthread in c++
- Console output in a Qt GUI app?
- “Symbol(s) not found for architecture x86_64” on QtCreator project
- Error: Could not resolve SDK path for ‘macosx10.8’
- How do I construct an ISO 8601 datetime in C++?
- Virtual dispatch implementation details
- What are consequences of forcing QObject as a parent of QWidget?
- QTableView printing
- Can’t downcast because class is not polymorphic?
- How to call function after window is shown?
- QT QWebEnginePage::setWebChannel() transport object
- Sort filenames naturally with Qt