|qmake:||QT += axcontainer|
|void||changeEvent(int *e) override|
|void||connectNotify(const int &signal) override|
|virtual bool||createHostWindow(bool initialized)|
|bool||createHostWindow(bool initialized, const int &data)|
|void||resizeEvent(int *) override|
|virtual bool||translateKeyEvent(int message, int keycode) const|
|virtual bool||initialize(IUnknown **ptr) override|
A QAxWidget can be instantiated as an empty object, with the name of the ActiveX control it should wrap, or with an existing interface pointer to the ActiveX control. The ActiveX control's
properties, methods and events which only use QAxBase supported data types, become available as Qt properties, slots and signals. The base class QAxBase provides an
API to access the ActiveX directly through the
QAxWidget is a QWidget and can mostly be used as such, e.g. it can be organized in a widget hierarchy and layouts or act as an event filter. Standard widget properties, e.g. enabled are supported, but it depends on the ActiveX control to implement support for ambient properties like e.g. palette or font. QAxWidget tries to provide the necessary hints.
However, you cannot reimplement Qt-specific event handlers like mousePressEvent or keyPressEvent and expect them to be called reliably. The embedded control covers the QAxWidget completely, and usually handles the user interface itself. Use control-specific APIs (i.e. listen to the signals of the control), or use standard COM techniques like window procedure subclassing.
Warning: You can subclass QAxWidget, but you cannot use the
Q_OBJECT macro in the subclass (the generated moc-file will not compile), so you cannot add further signals,
slots or properties. This limitation is due to the metaobject information generated in runtime. To work around this problem, aggregate the QAxWidget as a member of the QObject subclass.
Creates the client site for the ActiveX control, and returns true if the control could be embedded successfully, otherwise returns false. If initialized is true the control has already been initialized.
This function is called by initialize(). If you reimplement initialize to customize the actual control instantiation, call this function in your reimplementation to have the control embedded by the default client side. Creates the client site for the ActiveX control, and returns true if the control could be embedded successfully, otherwise returns false.
Creates the client site for the ActiveX control, and returns true if the control could be embedded successfully, otherwise returns false. If initialized is false the control will be initialized using the data. The control will be initialized through either IPersistStreamInit or IPersistStorage interface.
This function was introduced in Qt 4.4.
Reimplemented from QAxBase::initialize().
To initialize the control before it is activated, reimplement this function and add your initialization code before you call createHostWindow(true).
This function was introduced in Qt 4.2.
Reimplement this function to pass certain key events to the ActiveX control. message is the Window message identifier specifying the message type (ie. WM_KEYDOWN), and keycode is the virtual keycode (ie. VK_TAB).
If the function returns true the key event is passed on to the ActiveX control, which then either processes the event or passes the event on to Qt.
If the function returns false the processing of the key event is ignored by ActiveQt, ie. the ActiveX control might handle it or not.
The default implementation returns true for the following cases:
|All keycodes||VK_MENU||VK_TAB, VK_DELETE and all non-arrow-keys in combination with VK_SHIFT, VK_CONTROL or VK_MENU|
This table is the result of experimenting with popular ActiveX controls, ie. Internet Explorer and Microsoft Office applications, but for some controls it might require modification.