The Qt callback system uses what they
call signals and slots. This system is generated by a precompiler
called moc.exe.
Classes deriving from Qt::QObject requiring signals/slots
must have the Q_Object macros in their declaration (see qttestwidget.h).
Each header using the Q_OBJECT macro must have a Custom Build Step
operation to ensure the file is correctly parsed by moc.exe. See
the comment on ortoolqttest_tool.h and the custom build step on qttestwidget.h.
This generates a "moc file" (moc_qttestwidget.cxx) containing all
runtime information (signals/slots, etc.) and it must be included
in your project so that linking works properly.
Qt Assistant generates .ui files (XML
files). These must be processed by moc.exe. See Custom Build Step
in qttest.ui. This operation generates ui_qttestwidget.h, and this
generated file must be included in your project.
To "bridge" between Qt UI and ORSDK UI,
we have created a control called a FBWidgetHolder.
This must be used to contain your Qt UI. This control must have
a "Creator" function assigned. The Creator function is called, when
needed, to instantiate a Qt widget. See ortoolqttest_tool.cxx.
