diff options
| -rw-r--r-- | src/activeqt/container/qaxbase.cpp | 3 | ||||
| -rw-r--r-- | src/activeqt/doc/src/examples/dotnet.qdoc | 4 |
2 files changed, 4 insertions, 3 deletions
diff --git a/src/activeqt/container/qaxbase.cpp b/src/activeqt/container/qaxbase.cpp index 8c70fe1..e97dd91 100644 --- a/src/activeqt/container/qaxbase.cpp +++ b/src/activeqt/container/qaxbase.cpp @@ -921,6 +921,9 @@ bool QAxBase::setControl(const QString &c) return true; } +/*! + Returns the ActiveX control. +*/ QString QAxBase::control() const { return d->ctrl; diff --git a/src/activeqt/doc/src/examples/dotnet.qdoc b/src/activeqt/doc/src/examples/dotnet.qdoc index 5fe1466..d9f09af 100644 --- a/src/activeqt/doc/src/examples/dotnet.qdoc +++ b/src/activeqt/doc/src/examples/dotnet.qdoc @@ -305,9 +305,7 @@ in the APIs can only be those supported by ActiveQt and COM. However, since this includes subclasses of QObject and QWidget we can wrap any of our datatypes into a QObject subclass to make its API - available to .NET. This has the positive side effect that the same - API is automatically available when using \l {Qt Script} to automate - Qt applications and to COM clients in general. + available to .NET. When using the "IJW" method, in principle the only limitation is the time required to write the wrapper classes and data type conversion |