diff options
Diffstat (limited to 'doc/html/qaxserver.html')
| -rw-r--r-- | doc/html/qaxserver.html | 34 |
1 files changed, 17 insertions, 17 deletions
diff --git a/doc/html/qaxserver.html b/doc/html/qaxserver.html index 766a1e04..ad20e4c4 100644 --- a/doc/html/qaxserver.html +++ b/doc/html/qaxserver.html @@ -141,7 +141,7 @@ body { background: #ffffff; color: black; } <p> <h2> Introduction </h2> <a name="1"></a><p> The TQAxServer module provides a static library implementing the -functions retquired to turn a standard TQt binary into an ActiveX +functions required to turn a standard TQt binary into an ActiveX control server. <p> This module is part of the <a href="activeqt.html">ActiveTQt framework</a>. (To incorporate ActiveX controls in a TQt @@ -195,7 +195,7 @@ You can modify these files as long as it includes any file as the type library entry, ie. you can add version information or use a different toolbox icon. <p> The <tt>activeqt</tt> configuration will cause the <tt>qmake</tt> tool to add the -retquired build steps to the build system: +required build steps to the build system: <ul> <li> link the binary against <tt>qaxserver.lib</tt> <li> generate an interface definition and link the type library into @@ -226,7 +226,7 @@ continue to run. <p> An in-process server is usually smaller and has faster startup time. The communication between client and server is done directly through virtual function calls and does not introduce the overhead -retquired for remote procedure calls. But if the server crashes the +required for remote procedure calls. But if the server crashes the client application is likely to crash as well. <p> Both server types can use TQt either as a shared library, or statically linked into the server binary. @@ -259,7 +259,7 @@ Microsoft Visual C++ 6.0 compiler. <a name="4-1-1-1"></a><p> When the error occurs in code that uses the <a href="qaxfactory.html#TQAXFACTORY_DEFAULT">TQAXFACTORY_DEFAULT</a> macro, the widget class had no constructor that can be used by the default factory. Either add a standard widget constructor or -implement a custom factory that doesn't retquire one. +implement a custom factory that doesn't require one. <p> When the error occurs in code that uses the <a href="qaxfactory.html#TQAXFACTORY_EXPORT">TQAXFACTORY_EXPORT</a> macro, the <a href="qaxfactory.html">TQAxFactory</a> subclass had no appropriate constructor. Provide a public class constructor like @@ -304,18 +304,18 @@ of the binary to make it into an ActiveX server. <li> Attach the type library as a binary resource to the server <li> Register the server </ul> -<p> For this to work the server has to meet some retquirements: +<p> For this to work the server has to meet some requirements: <p> <ul> <li> All controls exposed can be created with nothing but a <a href="qapplication.html">TQApplication</a> instance being present <li> The initial linking of the server includes a temporary type library resource -<li> All dependencies retquired to run the server are in the system path +<li> All dependencies required to run the server are in the system path (or in the path used by the calling environment; note that Visual Studio has it's own set of environment variables listed in the Tools|Options|Directories dialog). </ul> -<p> If those retquirements are not met one ore more of the following +<p> If those requirements are not met one ore more of the following errors are likely to occure: <p> <h5> The server executable crashes </h5> @@ -341,7 +341,7 @@ the interface definition, and to register the server. If a dynamic link library the server links against is not in the path this might fail (e.g. Visual Studio calls the server using the enivronment settings specified in the "Directories" option). Make -sure that all DLLs retquired by your server are located in a +sure that all DLLs required by your server are located in a directory that is listed in the path as printed in the error message box. <p> <h5> The Server does not respond @@ -386,7 +386,7 @@ or any existing TQWidget subclass: <a href="metaobjects.html#Q_OBJECT">Q_OBJECT</a> </pre> -<p> The <a href="metaobjects.html#Q_OBJECT">Q_OBJECT</a> macro is retquired to provide the <a href="metaobjects.html#meta-object">meta object</a> information +<p> The <a href="metaobjects.html#Q_OBJECT">Q_OBJECT</a> macro is required to provide the <a href="metaobjects.html#meta-object">meta object</a> information about the widget to the ActiveTQt framework. Use the <tt>Q_PROPERTY</tt> macro to declare properties for the ActiveX control: <p> <pre> @@ -640,7 +640,7 @@ server must export an implementation of a <a href="qaxfactory.html">TQAxFactory< default factory when the server provides only a single ActiveX control, and implement a subclass of TQAxFactory to provide multiple ActiveX controls. The default factory is available -through a macro that takes the identifiers COM retquires to locate +through a macro that takes the identifiers COM requires to locate the ActiveX control on the target system: <p> <pre> TQAXFACTORY_DEFAULT ( MyActiveX, @@ -734,7 +734,7 @@ make the server available to the browser used to view your page, and you need to specify the location of the server package in your page. <p> To specify the location of a server, use the CODEBASE attribute in the OBJECT tag of your web-site. The value can point to the server -file itself, to an <tt>INF</tt> file listing other files the server retquires +file itself, to an <tt>INF</tt> file listing other files the server requires (e.g. the TQt DLL), or a compressed <tt>CAB</tt> archive. <p> INF and CAB files are documented in almost every book available about ActiveX and COM programming as well as in the MSDN library and various @@ -873,8 +873,8 @@ Ie. the default property of a push button would be "text". Ie. the default signal of a push button would be "clicked". <tr bgcolor="#f0f0f0"> <td valign="top">LicenseKey -<td valign="top">Object creation retquires the specified license key. The key can be -empty to retquire a licensed machine. By default classes are not +<td valign="top">Object creation requires the specified license key. The key can be +empty to require a licensed machine. By default classes are not licensed. Also see the following section. <tr bgcolor="#d0d0d0"> <td valign="top">StockEvents @@ -951,14 +951,14 @@ macro. }; </pre> -The key is retquired to be able to create an instance of <tt>MyLicensedControl</tt> +The key is required to be able to create an instance of <tt>MyLicensedControl</tt> on a machine that is not licensed itself. The licensed developer can now redistributes the server binary with his application, which creates the control using the value of "LicenseKey", while users of the application cannot create the control without the license key. <p> If a single license key for the control is not sufficient (ie. you want differnet developers to receive different license keys) you can specify an -empty key to indicate that the control retquires a license, and reimplement +empty key to indicate that the control requires a license, and reimplement <a href="qaxfactory.html#validateLicenseKey">TQAxFactory::validateLicenseKey</a>() to verify that a license exists on the system (ie. through a license file). <p> <h3> More Interfaces @@ -1056,10 +1056,10 @@ Microsoft OLE needs to marshal user defined types by reference (ByRef), and cannot marshal them by value (ByVal). This is why const-references and object parameters are not supported for <a href="qrect.html">TQRect</a>, <a href="qsize.html">TQSize</a> and <a href="qpoint.html">TQPoint</a>. Also note that -servers with this datatype retquire Windows 98 or DCOM 1.2 to be installed. +servers with this datatype require Windows 98 or DCOM 1.2 to be installed. <a href="#footnote-call3">Back...</a> <li><a name="footnote4"></a> -This is not retquired, but gives the client more control over +This is not required, but gives the client more control over the ActiveX control. <a href="#footnote-call4">Back...</a></ol> </hr> |