diff options
Diffstat (limited to 'doc/html/motif-extension.html')
| -rw-r--r-- | doc/html/motif-extension.html | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/doc/html/motif-extension.html b/doc/html/motif-extension.html index 0e9931e85..19d0af80d 100644 --- a/doc/html/motif-extension.html +++ b/doc/html/motif-extension.html @@ -45,8 +45,8 @@ versions of TQt. <p> The TQt Motif Extension consists of the following classes: <p> <ul> <li> <a href="qmotif.html">TQMotif</a> - Provides the basis of the TQt Motif Extension. -<li> <a href="qmotifwidget.html">TQMotifWidget</a> - Provides the <a href="qwidget.html">TQWidget</a> API for Motif widgets. -<li> <a href="qmotifdialog.html">TQMotifDialog</a> - Provides the <a href="qdialog.html">TQDialog</a> API for Motif dialogs. +<li> <a href="qmotifwidget.html">TQMotifWidget</a> - Provides the <a href="ntqwidget.html">TQWidget</a> API for Motif widgets. +<li> <a href="qmotifdialog.html">TQMotifDialog</a> - Provides the <a href="ntqdialog.html">TQDialog</a> API for Motif dialogs. <li> <a href="qxtwidget.html">TQXtWidget</a> - The Xt/Motif integration widget from the previous Xt/Motif extension. This class is unsupported and has many known problems and limitations. It is provided only to keep existing source @@ -64,7 +64,7 @@ complete migration of a Motif based program to the TQt toolkit. <a name="2"></a><p> <h3> Incorrect CDE Color Scheme </h3> <a name="2-1"></a><p> <a href="qmotifwidget.html">TQMotifWidget</a> and <a href="qmotifdialog.html">TQMotifDialog</a> will use the same Visual, Colormap -and color depth that <a href="qapplication.html">TQApplication</a> uses. When using CDE, the color +and color depth that <a href="ntqapplication.html">TQApplication</a> uses. When using CDE, the color scheme may be incorrect when using a Visual, Colormap and color depth that is not the default. To work around this problem, add the following resource string to your startup files (for example, @@ -81,9 +81,9 @@ headers from this extension, and all Xt/Motif and X11 headers last. For example: <p> <pre> // TQt headers first - #include <<a href="qapplication-h.html">qapplication.h</a>> - #include <<a href="qpushbutton-h.html">qpushbutton.h</a>> - #include <<a href="qsocket-h.html">qsocket.h</a>> + #include <<a href="qapplication-h.html">ntqapplication.h</a>> + #include <<a href="qpushbutton-h.html">ntqpushbutton.h</a>> + #include <<a href="qsocket-h.html">ntqsocket.h</a>> ... // TQMotif* headers next @@ -100,7 +100,7 @@ For example: <p> <h3> Multiple Screen Support </h3> -<a name="2-3"></a><p> <a href="qmotifwidget.html">TQMotifWidget</a> can be used together with <a href="qdesktopwidget.html">TQDesktopWidget</a> to create +<a name="2-3"></a><p> <a href="qmotifwidget.html">TQMotifWidget</a> can be used together with <a href="ntqdesktopwidget.html">TQDesktopWidget</a> to create top-level windows on multiple screens. A common mistake is to create a TQMotifWidget on a non-default screen while the Xt/Motif widgets are created on the default screen. The solution is to specify the screen @@ -112,7 +112,7 @@ to both TQMotifWidget and the Xt/Motif child. For example: // make sure both TQMotifWidget and the XmMainWindow are on screen 1 XtSetArg(args[0], XtNscreen, ScreenOfDisplay(dpy, 1)); <a href="qmotifwidget.html">TQMotifWidget</a> *toplevel = - new <a href="qmotifwidget.html">TQMotifWidget</a>(TQApplication::<a href="qapplication.html#desktop">desktop</a>()->screen(1), + new <a href="qmotifwidget.html">TQMotifWidget</a>(TQApplication::<a href="ntqapplication.html#desktop">desktop</a>()->screen(1), xmMainWindowWidgetClass, args, 1, "mainwindow"); </pre> |