From 4161606c301841f973f0319f46e6853c4a3fe906 Mon Sep 17 00:00:00 2001 From: Michele Calgaro Date: Thu, 3 Oct 2024 20:48:26 +0900 Subject: [PATCH] Remove documentation for Motif extension classes. Those classes are not included in tqt3 source code Signed-off-by: Michele Calgaro --- MANIFEST | 1 - doc/editions.doc | 7 - doc/html/annotated.html | 3 - doc/html/classes.html | 14 +- doc/html/customstyles.html | 2 +- doc/html/dnd.html | 2 +- doc/html/editions.html | 12 - doc/html/examples.html | 5 - doc/html/functions.html | 29 +- doc/html/guibooks.html | 2 +- doc/html/headers.html | 4 - doc/html/hierarchy.html | 5 - doc/html/index | 33 --- doc/html/index.html | 1 - doc/html/modules.html | 1 - doc/html/motif-customwidget-example.html | 148 ---------- doc/html/motif-dialog-example.html | 237 --------------- doc/html/motif-examples.html | 52 ---- doc/html/motif-extension.html | 127 -------- doc/html/motif-todo.png | Bin 4392 -> 0 bytes doc/html/motif-walkthrough-1.html | 98 ------- doc/html/motif-walkthrough-10.html | 103 ------- doc/html/motif-walkthrough-2.html | 101 ------- doc/html/motif-walkthrough-3.html | 178 ------------ doc/html/motif-walkthrough-4.html | 102 ------- doc/html/motif-walkthrough-5.html | 109 ------- doc/html/motif-walkthrough-6.html | 129 -------- doc/html/motif-walkthrough-7.html | 214 -------------- doc/html/motif-walkthrough-8.html | 212 -------------- doc/html/motif-walkthrough-9.html | 104 ------- doc/html/motif-walkthrough.html | 150 ---------- doc/html/opengl.html | 2 +- doc/html/overviews-list.html | 1 - doc/html/pictures.html | 2 +- doc/html/propertydocs | 8 +- doc/html/qt.dcf | 79 ----- doc/html/qxtwidget-h.html | 110 ------- doc/html/qxtwidget-members.html | 338 --------------------- doc/html/qxtwidget.html | 147 ---------- doc/html/titleindex | 27 -- doc/html/tqcdestyle.html | 4 +- doc/html/tqcolorgroup.html | 2 +- doc/html/tqcombobox.html | 10 +- doc/html/tqdialog.html | 4 +- doc/html/tqeventloop.html | 5 +- doc/html/tqlineedit.html | 2 +- doc/html/tqlistview.html | 4 +- doc/html/tqmenubar.html | 2 +- doc/html/tqmenudata.html | 2 +- doc/html/tqmessagebox.html | 2 +- doc/html/tqmotif-h.html | 112 ------- doc/html/tqmotif-members.html | 108 ------- doc/html/tqmotif.html | 115 -------- doc/html/tqmotifdialog-h.html | 153 ---------- doc/html/tqmotifdialog-members.html | 355 ----------------------- doc/html/tqmotifdialog.html | 205 ------------- doc/html/tqmotifplusstyle.html | 2 +- doc/html/tqmotifstyle.html | 8 +- doc/html/tqmotifwidget-h.html | 115 -------- doc/html/tqmotifwidget-members.html | 338 --------------------- doc/html/tqmotifwidget.html | 115 -------- doc/html/tqpalette.html | 2 +- doc/html/tqpopupmenu.html | 2 +- doc/html/tqscrollbar.html | 4 +- doc/html/tqsgistyle.html | 4 +- doc/html/tqslider.html | 2 +- doc/html/tqstyle.html | 4 +- doc/html/tqwidget.html | 8 +- doc/html/whatsthis | 3 - doc/indices.doc | 35 --- doc/man/man3/TQMotif.3qt | 1 - doc/man/man3/TQMotifDialog.3qt | 1 - doc/man/man3/TQMotifWidget.3qt | 1 - doc/man/man3/tqdialog.3qt | 2 +- doc/man/man3/tqeventloop.3qt | 4 +- doc/man/man3/tqmotif.3qt | 114 -------- doc/man/man3/tqmotifdialog.3qt | 178 ------------ doc/man/man3/tqmotifwidget.3qt | 86 ------ doc/man/man3/tqwidget.3qt | 6 +- doc/modules.doc | 1 - doc/overviews-list.doc | 2 - src/kernel/tqeventloop.cpp | 4 +- 82 files changed, 64 insertions(+), 4962 deletions(-) delete mode 100644 doc/html/motif-customwidget-example.html delete mode 100644 doc/html/motif-dialog-example.html delete mode 100644 doc/html/motif-examples.html delete mode 100644 doc/html/motif-extension.html delete mode 100644 doc/html/motif-todo.png delete mode 100644 doc/html/motif-walkthrough-1.html delete mode 100644 doc/html/motif-walkthrough-10.html delete mode 100644 doc/html/motif-walkthrough-2.html delete mode 100644 doc/html/motif-walkthrough-3.html delete mode 100644 doc/html/motif-walkthrough-4.html delete mode 100644 doc/html/motif-walkthrough-5.html delete mode 100644 doc/html/motif-walkthrough-6.html delete mode 100644 doc/html/motif-walkthrough-7.html delete mode 100644 doc/html/motif-walkthrough-8.html delete mode 100644 doc/html/motif-walkthrough-9.html delete mode 100644 doc/html/motif-walkthrough.html delete mode 100644 doc/html/qxtwidget-h.html delete mode 100644 doc/html/qxtwidget-members.html delete mode 100644 doc/html/qxtwidget.html delete mode 100644 doc/html/tqmotif-h.html delete mode 100644 doc/html/tqmotif-members.html delete mode 100644 doc/html/tqmotif.html delete mode 100644 doc/html/tqmotifdialog-h.html delete mode 100644 doc/html/tqmotifdialog-members.html delete mode 100644 doc/html/tqmotifdialog.html delete mode 100644 doc/html/tqmotifwidget-h.html delete mode 100644 doc/html/tqmotifwidget-members.html delete mode 100644 doc/html/tqmotifwidget.html delete mode 100644 doc/man/man3/TQMotif.3qt delete mode 100644 doc/man/man3/TQMotifDialog.3qt delete mode 100644 doc/man/man3/TQMotifWidget.3qt delete mode 100644 doc/man/man3/tqmotif.3qt delete mode 100644 doc/man/man3/tqmotifdialog.3qt delete mode 100644 doc/man/man3/tqmotifwidget.3qt diff --git a/MANIFEST b/MANIFEST index fbaf0ae6..1dec82dd 100644 --- a/MANIFEST +++ b/MANIFEST @@ -11,7 +11,6 @@ bin Place for TQt executables (moc, uic, etc.) config.tests Qt configuration system doc Qt documentation in HTML and manpage format examples Qt example programs -extensions Qt extensions (Browser Plugin, Xt/Motif support, etc.) include Qt include files lib Place for the TQt libraries mkspecs Platform/compiler configuration files diff --git a/doc/editions.doc b/doc/editions.doc index 6df02c4f..86543b00 100644 --- a/doc/editions.doc +++ b/doc/editions.doc @@ -118,13 +118,6 @@ Editions. X - - TQMotif extension
- Motif co-existence and migration support. -
- - X - */ diff --git a/doc/html/annotated.html b/doc/html/annotated.html index 60709674..56285525 100644 --- a/doc/html/annotated.html +++ b/doc/html/annotated.html @@ -240,11 +240,8 @@ body { background: #ffffff; color: black; } TQMetaPropertyStores meta data about a property TQMimeSourceAbstraction of objects which provide formatted data of a certain MIME type TQMimeSourceFactoryExtensible provider of mime-typed data -TQMotifThe basis of the Motif Extension -TQMotifDialogThe TQDialog API for Motif-based dialogs TQMotifPlusStyleMore sophisticated Motif-ish look and feel TQMotifStyleMotif look and feel -TQMotifWidgetThe TQWidget API for Xt/Motif widgets TQMouseEventParameters that describe a mouse event TQMoveEventEvent parameters for move events TQMovieIncremental loading of animations or images, signalling as it progresses diff --git a/doc/html/classes.html b/doc/html/classes.html index a0122823..e7d97b53 100644 --- a/doc/html/classes.html +++ b/doc/html/classes.html @@ -625,8 +625,8 @@ classes, see TQt's Main Classes. TQGbkCodec -TQMotif -* + + TQSqlDatabase TQWidgetPlugin @@ -636,8 +636,8 @@ classes, see TQt's Main Classes. -TQMotifDialog -* + + TQSqlDriver TQWidgetStack @@ -669,8 +669,8 @@ classes, see TQt's Main Classes. TQGLayoutIterator -TQMotifWidget -* + + TQSqlError TQWizard @@ -961,8 +961,6 @@ classes, see TQt's Main Classes. -

* Extension classes of Motif. -


diff --git a/doc/html/customstyles.html b/doc/html/customstyles.html index 9bca441c..dab94e51 100644 --- a/doc/html/customstyles.html +++ b/doc/html/customstyles.html @@ -35,7 +35,7 @@ body { background: #ffffff; color: black; }

A style in TQt implements the look and feel found in a GUI for a particular platform. For example, Windows platforms may use the -Windows or Windows-XP style, Unix platforms may use the Motif style, +Windows or Windows-XP style, Unix platforms may use the Motif style, and so on.

This is a short guide that describes the steps that are necessary to get started creating and using custom styles with the TQt 3.x style diff --git a/doc/html/dnd.html b/doc/html/dnd.html index 53cc80fd..b5c4170b 100644 --- a/doc/html/dnd.html +++ b/doc/html/dnd.html @@ -339,7 +339,7 @@ TQt has facilities for translating proprietary clipboard formats to and from MIME types. This interface will be made public at some time, but if you need to do such translations now, contact your TQt Technical Support service. -

On X11, TQt also supports drops via the Motif Drag&Drop Protocol. The +

On X11, TQt also supports drops via the Motif Drag&Drop Protocol. The implementation incorporates some code that was originally written by Daniel Dardailler, and adapted for TQt by Matt Koss <koss@napri.sk> and Trolltech. Here is the original copyright notice: diff --git a/doc/html/editions.html b/doc/html/editions.html index d8b9915e..bf32ca1f 100644 --- a/doc/html/editions.html +++ b/doc/html/editions.html @@ -107,18 +107,6 @@ Well-formed XML parser with SAX interface and DOM Level 1. X - -
- -X - - -TQMotif extension
-Motif co-existence and migration support. -
- -X -

diff --git a/doc/html/examples.html b/doc/html/examples.html index 33046591..9bbea63e 100644 --- a/doc/html/examples.html +++ b/doc/html/examples.html @@ -58,11 +58,6 @@ in a line-by-line coverage please refer to the tutorials

  • Table examples
  • SQL examples -

    TQt Extensions: Assorted Examples -

    -

    Miscellaneous Examples

    diff --git a/doc/html/functions.html b/doc/html/functions.html index cec33522..1d495d7d 100644 --- a/doc/html/functions.html +++ b/doc/html/functions.html @@ -55,8 +55,7 @@ abort: TQDir

  • accel: TQAction TQButton TQCheckBox TQMenuData TQPopupMenu TQPushButton TQRadioButton
  • accept: TQCloseEvent TQContextMenuEvent TQDialog TQDragMoveEvent TQDropEvent TQIMEvent TQIconDragEvent TQKeyEvent TQMouseEvent TQSocketDevice TQTabletEvent TQWheelEvent
  • acceptAction: - TQDropEvent
  • acceptCallback: - TQMotifDialog
  • acceptDrop: + TQDropEvent
  • acceptDrop: TQIconViewItem TQListViewItem
  • acceptDrops: TQWidget
  • accum: TQGLFormat
  • action: @@ -153,8 +152,7 @@ abort: TQDragMoveEvent
  • append: TQCString TQIconDrag TQPtrList TQSqlCursor TQSqlIndex TQSqlRecord TQString TQTextEdit TQValueList TQValueVector TQXmlAttributes
  • appendChild: TQDomNode
  • appendData: - TQDomCharacterData
  • applicationContext: - TQMotif
  • applicationDirPath: + TQDomCharacterData
  • applicationDirPath: TQApplication
  • applicationFilePath: TQApplication
  • applyButtonPressed: TQTabDialog
  • appropriate: @@ -702,8 +700,7 @@ dark: TQGLContext
  • dialMoved: TQDial
  • dialPressed: TQDial
  • dialReleased: - TQDial
  • dialog: - TQMotifDialog
  • digitValue: + TQDial
  • digitValue: TQChar
  • dimensionChange: TQGridView
  • dir: TQFileDialog TQFileInfo
  • dirEntered: @@ -1250,7 +1247,7 @@ icon: TQCloseEvent TQContextMenuEvent TQDropEvent TQIMEvent TQIconDragEvent TQKeyEvent TQMouseEvent TQTabletEvent TQWheelEvent
  • isActionAccepted: TQDropEvent
  • isActive: TQAccessible TQCanvasItem TQPainter TQSqlQuery TQSqlResult TQTableSelection TQTimer
  • isActiveWindow: - TQWidget TQXtWidget
  • isAnchor: + TQWidget
  • isAnchor: TQStyleSheetItem
  • isAsynchronous: TQIODevice
  • isAttr: TQDomAttr TQDomNode
  • isAutoRepeat: @@ -1653,8 +1650,7 @@ m11: TQDir TQFtp TQUrlOperator
  • mode: TQFileDialog TQIODevice TQLCDNumber TQSqlCursor
  • modificationChanged: TQTextEdit
  • month: - TQDate
  • motifWidget: - TQMotifWidget
  • mouseButtonClicked: + TQDate
  • mouseButtonClicked: TQIconView TQListBox TQListView
  • mouseButtonPressed: TQIconView TQListBox TQListView
  • mouseDoubleClickEvent: TQWidget
  • mouseGrabber: @@ -2085,8 +2081,7 @@ rBottom: TQEventLoop
  • registerSqlDriver: TQSqlDatabase
  • rehighlight: TQSyntaxHighlighter
  • reject: - TQDialog
  • rejectCallback: - TQMotifDialog
  • release: + TQDialog
  • release: TQSessionManager
  • releaseKeyboard: TQWidget
  • releaseMouse: TQWidget
  • released: @@ -2297,7 +2292,7 @@ sRect: TQDropEvent
  • setActive: TQCanvasItem TQPalette TQSqlResult
  • setActiveItem: TQPopupMenu
  • setActiveWindow: - TQWidget TQXtWidget
  • setAddress: + TQWidget
  • setAddress: TQHostAddress
  • setAddressReusable: TQSocketDevice
  • setAdvancePeriod: TQCanvas
  • setAlignment: @@ -3000,8 +2995,7 @@ sRect: TQListViewItem TQPrinter
  • shadow: TQColorGroup
  • shape: TQCursor TQTabBar
  • shear: - TQPainter TQWMatrix
  • shell: - TQMotifDialog
  • shortDayName: + TQPainter TQWMatrix
  • shortDayName: TQDate
  • shortMonthName: TQDate
  • shortcutKey: TQAccel
  • show: @@ -3487,8 +3481,8 @@ x: TQPaintDevice
  • x11DefaultVisual: TQPaintDevice
  • x11Depth: TQPaintDevice
  • x11Display: - TQMotif TQPaintDevice
  • x11Event: - TQMotifWidget TQWidget TQXtWidget
  • x11EventFilter: + TQPaintDevice
  • x11Event: + TQWidget
  • x11EventFilter: TQApplication
  • x11ProcessEvent: TQApplication
  • x11Screen: TQPaintDevice
  • x11SetAppDpiX: @@ -3498,8 +3492,7 @@ x: TQBitmap TQImage TQPainter TQPixmap
  • xFormDev: TQPainter
  • xTilt: TQTabletEvent
  • xVelocity: - TQCanvasItem
  • xtWidget: - TQXtWidget
  • + TQCanvasItem
  • y: TQCanvasItem TQContextMenuEvent TQIconViewItem TQMouseEvent TQPoint TQRect TQTabletEvent TQWheelEvent TQWidget
  • yTilt: TQTabletEvent
  • yVelocity: diff --git a/doc/html/guibooks.html b/doc/html/guibooks.html index 981f15e8..9612d5ca 100644 --- a/doc/html/guibooks.html +++ b/doc/html/guibooks.html @@ -51,7 +51,7 @@ supposed to use. alphabetical dictionary of widgets and other user interface elements, with comprehensive coverage of each. Each chapter covers one widget or other element, contains the most important recommendation from the -Macintosh, Windows and Motif style guides, notes about common +Macintosh, Windows and Motif style guides, notes about common problems, comparison with other widgets that can serve some of the same roles as this one, etc.

    (Read more or buy it.) diff --git a/doc/html/headers.html b/doc/html/headers.html index b71e332a..6abd63c2 100644 --- a/doc/html/headers.html +++ b/doc/html/headers.html @@ -140,11 +140,8 @@ body { background: #ffffff; color: black; }

  • tqmessagebox.h
  • tqmetaobject.h
  • tqmime.h -
  • tqmotif.h -
  • tqmotifdialog.h
  • tqmotifplusstyle.h
  • tqmotifstyle.h -
  • tqmotifwidget.h
  • tqmovie.h
  • tqmultilineedit.h
  • tqmutex.h @@ -273,7 +270,6 @@ body { background: #ffffff; color: black; }
  • tqwmatrix.h
  • tqworkspace.h
  • tqxml.h -
  • qxtwidget.h diff --git a/doc/html/hierarchy.html b/doc/html/hierarchy.html index 419e69b5..19f6000d 100644 --- a/doc/html/hierarchy.html +++ b/doc/html/hierarchy.html @@ -323,8 +323,6 @@ classes in the TQt API.
  • TQEventLoop
  • TQFileIconProvider
  • TQLayout
  • TQPainter
  • TQPen diff --git a/doc/html/index b/doc/html/index index 5914351d..ce66e4c6 100644 --- a/doc/html/index +++ b/doc/html/index @@ -3,7 +3,6 @@ "A Complete Application Window with Actions" tqaction-application-example.html "A Complete Canvas Application" canvas-chart-example.html "A Directory Browser" dirview-example.html -"A Motif Dialog" motif-dialog-example.html "A Rectangle Draw \"Benchmark\"" forever-example.html "A Small Application for Testing Regular Expressions" regexptester-example.html "A Tiny Example Featuring a Toggle Action" toggleaction-example.html @@ -36,7 +35,6 @@ "Class Inheritance Hierarchy" hierarchy.html "Company Information" troll.html "Connect the Points" drawlines-example.html -"Continuing Development" motif-walkthrough-10.html "Conway's Game of Life" life-example.html "Cursors" cursor-example.html "Customized Layoutmanager" customlayout-example.html @@ -54,7 +52,6 @@ "Font Displayer" qfd-example.html "Format of the TQDataStream Operators" datastreamformat.html "GNU General Public License" gpl.html -"Getting Started" motif-walkthrough-1.html "Grouped Classes" groups.html "Header File Index" headers.html "Hello, World" hello-example.html @@ -101,7 +98,6 @@ "Pictures of Most TQt Widgets" pictures.html "Popup Widgets" popup-example.html "Porting to TQt 3.x" porting.html -"Preparing to Migrate the User Interface" motif-walkthrough-2.html "Presenting the GUI" tutorial2-05.html "Progress Bar" progressbar-example.html "Progress Bar and Dialog Example" progress-example.html @@ -4040,23 +4036,10 @@ "TQMimeSourceFactory::setText" tqmimesourcefactory.html#setText "TQMimeSourceFactory::takeDefaultFactory" tqmimesourcefactory.html#takeDefaultFactory "TQMimeSourceFactory::~TQMimeSourceFactory" tqmimesourcefactory.html#~TQMimeSourceFactory -"TQMotif" tqmotif.html -"TQMotif::applicationContext" tqmotif.html#applicationContext -"TQMotif::x11Display" tqmotif.html#x11Display -"TQMotif::~TQMotif" tqmotif.html#~TQMotif -"TQMotifDialog" tqmotifdialog.html -"TQMotifDialog::acceptCallback" tqmotifdialog.html#acceptCallback -"TQMotifDialog::dialog" tqmotifdialog.html#dialog -"TQMotifDialog::rejectCallback" tqmotifdialog.html#rejectCallback -"TQMotifDialog::shell" tqmotifdialog.html#shell -"TQMotifDialog::~TQMotifDialog" tqmotifdialog.html#~TQMotifDialog "TQMotifPlusStyle" tqmotifplusstyle.html "TQMotifStyle" tqmotifstyle.html "TQMotifStyle::setUseHighlightColors" tqmotifstyle.html#setUseHighlightColors "TQMotifStyle::useHighlightColors" tqmotifstyle.html#useHighlightColors -"TQMotifWidget" tqmotifwidget.html -"TQMotifWidget::motifWidget" tqmotifwidget.html#motifWidget -"TQMotifWidget::~TQMotifWidget" tqmotifwidget.html#~TQMotifWidget "TQMouseEvent" tqmouseevent.html "TQMouseEvent::accept" tqmouseevent.html#accept "TQMouseEvent::button" tqmouseevent.html#button @@ -7712,11 +7695,6 @@ "TQXmlSimpleReader::parseContinue" tqxmlsimplereader.html#parseContinue "TQXmlSimpleReader::setFeature" tqxmlsimplereader.html#setFeature "TQXmlSimpleReader::~TQXmlSimpleReader" tqxmlsimplereader.html#~TQXmlSimpleReader -"QXtWidget::isActiveWindow" qxtwidget.html#isActiveWindow -"QXtWidget::setActiveWindow" qxtwidget.html#setActiveWindow -"QXtWidget::x11Event" qxtwidget.html#x11Event -"QXtWidget::xtWidget" qxtwidget.html#xtWidget -"QXtWidget::~QXtWidget" qxtwidget.html#~QXtWidget "Q_ASSERT" ntqapplication.html#Q_ASSERT "TQ_CHECK_PTR" ntqapplication.html#TQ_CHECK_PTR "Qt" tqt.html @@ -7724,8 +7702,6 @@ "TQt Demo" demo-example.html "TQt Distribution Example" distributor-example.html "TQt Editions" editions.html -"TQt Motif Extension" motif-extension.html -"TQt Motif Extension - A Migration Walkthrough" motif-walkthrough.html "TQt Object Model" object.html "TQt Open Source Edition" opensourceedition.html "TQt Open Source Edition License Agreement" license.html @@ -7786,9 +7762,6 @@ "TQt::WindowState" tqt.html#WindowState "TQt::WindowsVersion" tqt.html#WindowsVersion "Range controls" rangecontrols-example.html -"Refactoring Existing Code" motif-walkthrough-7.html -"Replacing the Print Dialog" motif-walkthrough-9.html -"Replacing the View Widget" motif-walkthrough-8.html "Richtext" richtext-example.html "Rot13" rot-example.html "SQL Module" sql.html @@ -7834,13 +7807,8 @@ "Transformed Graphics Demo" xform-example.html "Tutorial #2" tutorial2.html "User Interface Compiler (uic)" uic.html -"Using Custom TQDialogs" motif-walkthrough-4.html -"Using Existing Dialogs with TQMotifDialog" motif-walkthrough-5.html -"Using TQt Main Window Classes" motif-walkthrough-6.html -"Using TQt Standard Dialogs" motif-walkthrough-3.html "Using menus" menu-example.html "Using the Meta Object Compiler" moc.html -"Using the Motif Event Loop" motif-customwidget-example.html "Walkthrough: A Simple Application" simple-application.html "Walkthrough: How to use the TQt SAX2 classes" xml-sax-walkthrough.html "Walkthrough: Using SAX2 features with the TQt XML classes" xml-sax-features-walkthrough.html @@ -7876,7 +7844,6 @@ "images" images.html "io" io.html "misc" misc.html -"motif-examples" motif-examples.html "multimedia" multimedia.html "network-examples" network-examples.html "objectmodel" objectmodel.html diff --git a/doc/html/index.html b/doc/html/index.html index f362b508..6f121372 100644 --- a/doc/html/index.html +++ b/doc/html/index.html @@ -148,7 +148,6 @@ Licenses & Credits diff --git a/doc/html/modules.html b/doc/html/modules.html index 954e2bd9..282ff6b9 100644 --- a/doc/html/modules.html +++ b/doc/html/modules.html @@ -50,7 +50,6 @@ with each Edition.
  • Table Module
  • Workspace (MDI) Module
  • XML Module -
  • TQMotif Extension

    diff --git a/doc/html/motif-customwidget-example.html b/doc/html/motif-customwidget-example.html deleted file mode 100644 index 613b0330..00000000 --- a/doc/html/motif-customwidget-example.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - -Using the Motif Event Loop - - - - - - - -
    - -Home - | -All Classes - | -Main Classes - | -Annotated - | -Grouped Classes - | -Functions -

    Using the Motif Event Loop

    - - -

    -

    -


    -

    Header -

    #ifndef MAINWINDOW_H
    -#define MAINWINDOW_H
    -
    -#include <tqmainwindow.h>
    -
    -
    -class TQMotifWidget;
    -
    -class MainWindow : public TQMainWindow
    -{
    -public:
    -    MainWindow();
    -
    -private:
    -    TQMotifWidget *customwidget;
    -};
    -
    -#endif // MAINWINDOW_H
    -
    - -


    -

    Implementation: -

    #include "mainwindow.h"
    -
    -#include <ntqapplication.h>
    -#include <tqmotif.h>
    -
    -
    -int main( int argc, char **argv )
    -{
    -    XtSetLanguageProc( NULL, NULL, NULL );
    -
    -    TQMotif integrator( "customwidget" );
    -    TQApplication app( argc, argv );
    -
    -    MainWindow mainwindow;
    -    app.setMainWidget( &mainwindow );
    -    mainwindow.show();
    -
    -    return app.exec();
    -}
    -
    - -

    #include "mainwindow.h"
    -
    -#include <ntqapplication.h>
    -#include <tqmenubar.h>
    -#include <tqpopupmenu.h>
    -#include <tqstatusbar.h>
    -
    -#include <tqmotifwidget.h>
    -
    -#include <Xm/Form.h>
    -#include <Xm/PushB.h>
    -#include <Xm/Text.h>
    -
    -
    -MainWindow::MainWindow()
    -    : TQMainWindow( 0, "mainwindow" )
    -{
    -    TQPopupMenu *filemenu = new TQPopupMenu( this );
    -    filemenu->insertItem( tr("&Quit"), tqApp, TQ_SLOT(quit()) );
    -
    -    menuBar()->insertItem( tr("&File"), filemenu );
    -    statusBar()->message( tr("This is a TQMainWindow with an XmText widget.") );
    -
    -    customwidget =
    -        new TQMotifWidget( this, xmFormWidgetClass, NULL, 0, "form" );
    -
    -    XmString str;
    -    Arg args[6];
    -
    -    str = XmStringCreateLocalized( "Push Button (XmPushButton)" );
    -    XtSetArg( args[0], XmNlabelString, str );
    -    XtSetArg( args[1], XmNleftAttachment, XmATTACH_FORM );
    -    XtSetArg( args[2], XmNrightAttachment, XmATTACH_FORM );
    -    XtSetArg( args[3], XmNbottomAttachment, XmATTACH_FORM );
    -    Widget button =
    -        XmCreatePushButton( customwidget->motifWidget(), "Push Button", args, 4 );
    -    XmStringFree( str );
    -
    -    XtSetArg( args[0], XmNeditMode, XmMULTI_LINE_EDIT );
    -    XtSetArg( args[1], XmNleftAttachment, XmATTACH_FORM );
    -    XtSetArg( args[2], XmNrightAttachment, XmATTACH_FORM );
    -    XtSetArg( args[3], XmNtopAttachment, XmATTACH_FORM );
    -    XtSetArg( args[4], XmNbottomAttachment, XmATTACH_WIDGET );
    -    XtSetArg( args[5], XmNbottomWidget, button );
    -    Widget texteditor =
    -        XmCreateScrolledText( customwidget->motifWidget(), "Text Editor", args, 6 );
    -
    -    XtManageChild( texteditor );
    -    XtManageChild( button );
    -
    -    setCentralWidget( customwidget );
    -
    -    resize( 400, 600 );
    -}
    -
    -
    - -

    See also TQMotif Support Extension. - - -


    - -
    Copyright © 2007 -TrolltechTrademarks -
    TQt 3.3.8
    -
    - diff --git a/doc/html/motif-dialog-example.html b/doc/html/motif-dialog-example.html deleted file mode 100644 index 470b1a0d..00000000 --- a/doc/html/motif-dialog-example.html +++ /dev/null @@ -1,237 +0,0 @@ - - - - - -A Motif Dialog - - - - - - - -
    - -Home - | -All Classes - | -Main Classes - | -Annotated - | -Grouped Classes - | -Functions -

    A Motif Dialog

    - - -

    -

    -


    -

    Header -

    #ifndef MAINWINDOW_H
    -#define MAINWINDOW_H
    -
    -#include <tqmotifwidget.h>
    -
    -
    -class MainWindow : public TQMotifWidget
    -{
    -public:
    -    MainWindow();
    -
    -    void showMotifDialog();
    -    void showTQtDialog();
    -};
    -
    -#endif // MAINWINDOW_H
    -
    - -


    -

    Implementation: -

    #include <ntqapplication.h>
    -#include <tqmotif.h>
    -
    -#include "mainwindow.h"
    -
    -
    -int main( int argc, char **argv )
    -{
    -    XtSetLanguageProc( NULL, NULL, NULL );
    -
    -    TQMotif integrator( "dialog" );
    -    TQApplication app( argc, argv );
    -
    -    MainWindow *mainwindow = new MainWindow;
    -    app.setMainWidget( mainwindow );
    -    mainwindow->show();
    -
    -    return app.exec();
    -}
    -
    - -

    #include "mainwindow.h"
    -#include "dialog.h"
    -
    -#include <Xm/MainW.h>
    -#include <Xm/RowColumn.h>
    -#include <Xm/CascadeB.h>
    -#include <Xm/PushB.h>
    -#include <Xm/PushBG.h>
    -#include <Xm/SeparatoG.h>
    -#include <Xm/Text.h>
    -#include <Xm/MessageB.h>
    -#include <Xm/Form.h>
    -#include <Xm/LabelG.h>
    -
    -#include <ntqapplication.h>
    -
    -
    -static void motifDialogCallback( Widget, XtPointer client_data, XtPointer )
    -{
    -    MainWindow *mw = (MainWindow *) client_data;
    -    mw->showMotifDialog();
    -}
    -
    -static void qtDialogCallback( Widget, XtPointer client_data, XtPointer )
    -{
    -    MainWindow *mw = (MainWindow *) client_data;
    -    mw->showTQtDialog();
    -}
    -
    -static void quitCallback( Widget, XtPointer client_data, XtPointer )
    -{
    -    MainWindow *mw = (MainWindow *) client_data;
    -    mw->close();
    -}
    -
    -
    -MainWindow::MainWindow()
    -    : TQMotifWidget( 0, xmMainWindowWidgetClass, NULL, 0, "mainwindow" )
    -{
    -    Widget menubar = XmCreateMenuBar( motifWidget(), "menubar", NULL, 0 );
    -    Widget filemenu = XmCreatePulldownMenu( menubar, "filemenu", NULL, 0 );
    -    Widget item;
    -
    -    item = XtVaCreateManagedWidget( "Motif Dialog...",
    -                                    xmPushButtonGadgetClass, filemenu,
    -                                    XmNmnemonic, 'C',
    -                                    NULL );
    -    XtAddCallback( item, XmNactivateCallback, motifDialogCallback, this );
    -
    -    item = XtVaCreateManagedWidget( "TQt Dialog...",
    -                                    xmPushButtonGadgetClass, filemenu,
    -                                    XmNmnemonic, 'Q',
    -                                    NULL );
    -    XtAddCallback( item, XmNactivateCallback, qtDialogCallback, this );
    -
    -    item = XtVaCreateManagedWidget( "sep",
    -                                    xmSeparatorGadgetClass, filemenu,
    -                                    NULL );
    -
    -    item = XtVaCreateManagedWidget( "Exit",
    -                                    xmPushButtonGadgetClass, filemenu,
    -                                    XmNmnemonic, 'x',
    -                                    NULL );
    -    XtAddCallback( item, XmNactivateCallback, quitCallback, this );
    -
    -    XmString str = XmStringCreateLocalized( "File" );
    -    item = XtVaCreateManagedWidget( "File",
    -                                    xmCascadeButtonWidgetClass, menubar,
    -                                    XmNlabelString, str,
    -                                    XmNmnemonic, 'F',
    -                                    XmNsubMenuId, filemenu,
    -                                    NULL );
    -    XmStringFree( str );
    -
    -    Arg args[2];
    -    XtSetArg( args[0], XmNeditMode, XmMULTI_LINE_EDIT );
    -    Widget texteditor =
    -        XmCreateScrolledText( motifWidget(), "texteditor",
    -                              args, 1 );
    -
    -    XtManageChild( menubar );
    -    XtManageChild( texteditor );
    -
    -    // pick a nice default size
    -    XtVaSetValues( motifWidget(),
    -                   XmNwidth, 400,
    -                   XmNheight, 300,
    -                   NULL );
    -
    -    setCaption( tr("TQMotif Dialog Example") );
    -
    -}
    -
    -void MainWindow::showMotifDialog()
    -{
    -    TQMotifDialog dialog( this, "custom dialog", TRUE );
    -    dialog.setCaption( tr("Custom Motif Dialog") );
    -
    -    Widget form = XmCreateForm( dialog.shell(), "custom motif dialog", NULL, 0 );
    -
    -    XmString str;
    -    Arg args[9];
    -
    -    str = XmStringCreateLocalized( "Close" );
    -    XtSetArg( args[0], XmNlabelString, str );
    -    XtSetArg( args[1], XmNshowAsDefault, True );
    -    XtSetArg( args[2], XmNleftAttachment, XmATTACH_POSITION );
    -    XtSetArg( args[3], XmNleftPosition, 40 );
    -    XtSetArg( args[4], XmNrightAttachment, XmATTACH_POSITION );
    -    XtSetArg( args[5], XmNrightPosition, 60 );
    -    XtSetArg( args[7], XmNbottomAttachment, XmATTACH_FORM );
    -    XtSetArg( args[6], XmNtopOffset, 10 );
    -    XtSetArg( args[8], XmNbottomOffset, 10 );
    -    Widget button = XmCreatePushButton( form, "Close", args, 9 );
    -    XmStringFree( str );
    -
    -    str =
    -        XmStringCreateLocalized( "This is a custom Motif-based dialog using\n"
    -                                 "TQMotifDialog with a TQWidget-based parent." );
    -    XtSetArg( args[0], XmNlabelString, str );
    -    XtSetArg( args[1], XmNleftAttachment, XmATTACH_FORM );
    -    XtSetArg( args[2], XmNrightAttachment, XmATTACH_FORM );
    -    XtSetArg( args[3], XmNtopAttachment, XmATTACH_FORM );
    -    XtSetArg( args[4], XmNbottomAttachment, XmATTACH_WIDGET );
    -    XtSetArg( args[5], XmNbottomWidget, button );
    -    XtSetArg( args[6], XmNtopOffset, 10 );
    -    XtSetArg( args[7], XmNbottomOffset, 10 );
    -    Widget label = XmCreateLabelGadget( form, "label", args, 8 );
    -    XmStringFree( str );
    -
    -    XtManageChild( button );
    -    XtManageChild( label );
    -    XtManageChild( form );
    -
    -    XtAddCallback( button, XmNactivateCallback,
    -                   (XtCallbackProc) TQMotifDialog::acceptCallback, &dialog );
    -
    -    dialog.exec();
    -}
    -
    -void MainWindow::showTQtDialog()
    -{
    -    // custom TQt-based dialog using a Motif-based parent
    -    CustomDialog customdialog( motifWidget(), "custom dialog", TRUE );
    -    customdialog.exec();
    -}
    -
    - -

    See also TQMotif Support Extension. - - -


    - -
    Copyright © 2007 -TrolltechTrademarks -
    TQt 3.3.8
    -
    - diff --git a/doc/html/motif-examples.html b/doc/html/motif-examples.html deleted file mode 100644 index 9ce8ed6b..00000000 --- a/doc/html/motif-examples.html +++ /dev/null @@ -1,52 +0,0 @@ - - - - - -TQMotif Support Extension - - - - - - - -
    - -Home - | -All Classes - | -Main Classes - | -Annotated - | -Grouped Classes - | -Functions -

    TQMotif Support Extension

    - - -

    The following example programs illustrate the use of the TQMotif Extension -assisting in the migration process of old Xt and Motif based code -to the more comfortable TQt toolkit. -

    For more information see the TQMotif -Support Extension documentation. - -

    -
    Using the Motif Event Loop -
    A Motif Dialog -
    - -


    - -
    Copyright © 2007 -TrolltechTrademarks -
    TQt 3.3.8
    -
    - diff --git a/doc/html/motif-extension.html b/doc/html/motif-extension.html deleted file mode 100644 index 86e53c7d..00000000 --- a/doc/html/motif-extension.html +++ /dev/null @@ -1,127 +0,0 @@ - - - - - -TQt Motif Extension - - - - - - - -
    - -Home - | -All Classes - | -Main Classes - | -Annotated - | -Grouped Classes - | -Functions -

    TQt Motif Extension

    - - -

    -

    This module is part of the TQt Enterprise -Edition and is not part of the Free or Non-Commercial -Editions. -

    Introduction -

    -

    The TQt Motif Extension assists the migration of old Xt and Motif based -applications to the more comfortable TQt toolkit. This extension -replaces the older Xt/Motif Support Extension included with earlier -versions of TQt. -

    The TQt Motif Extension consists of the following classes: -

      -
    • TQMotif - Provides the basis of the TQt Motif Extension. -
    • TQMotifWidget - Provides the TQWidget API for Motif widgets. -
    • TQMotifDialog - Provides the TQDialog API for Motif dialogs. -
    • TQXtWidget - 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 -working; it should not be used in new code. -
    -

    Additional Documentation -

    -

    -

    Common Problems -

    -

    Incorrect CDE Color Scheme -

    -

    TQMotifWidget and TQMotifDialog will use the same Visual, Colormap -and color depth that TQApplication 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, -$HOME/.dt/sessions/current/dt.resources): -

    -    *userColorObj: false
    -
    - -

    X11 Header Conflicts -

    -

    The X11 headers define some constants that conflict with the TQt -headers. The solution is to include all TQt headers first, followed by -headers from this extension, and all Xt/Motif and X11 headers last. -For example: -

    -    // TQt headers first
    -    #include <ntqapplication.h>
    -    #include <tqpushbutton.h>
    -    #include <tqsocket.h>
    -    ...
    -
    -    // TQMotif* headers next
    -    #include <tqmotif.h>
    -    #include <tqmotifdialog.h>
    -    #include <tqmotifwidget.h>
    -
    -    // Xt/Motif and X11 headers last
    -    #include <X11/Xlib.h>
    -    #include <Xt/Intrinsic.h>
    -    #include <Xm/Xm.h>
    -    ...
    -
    - -

    Multiple Screen Support -

    -

    TQMotifWidget can be used together with TQDesktopWidget 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 -to both TQMotifWidget and the Xt/Motif child. For example: -

    -    Display *dpy = TQMotif::x11Display();
    -    Arg args[1];
    -
    -    // make sure both TQMotifWidget and the XmMainWindow are on screen 1
    -    XtSetArg(args[0], XtNscreen, ScreenOfDisplay(dpy, 1));
    -    TQMotifWidget *toplevel =
    -        new TQMotifWidget(TQApplication::desktop()->screen(1),
    -                         xmMainWindowWidgetClass, args, 1, "mainwindow");
    -
    - -

    - -


    - -
    Copyright © 2007 -TrolltechTrademarks -
    TQt 3.3.8
    -
    - diff --git a/doc/html/motif-todo.png b/doc/html/motif-todo.png deleted file mode 100644 index d7634922f43ac2d102525de2d52249db5fa04aa1..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 4392 zcmaJ_c{o(<`#;7JLoo|2O2!^#i7aK$Ft+T4Y*R{J%aFZnV`Q(_mTd?xAri{IWr)fa zqAXeFRawfIi5QIKH@d#>^>+P!-|P3sxz4$t^E}UeKhNj+-1q04I5QK>Ax?fy000gd z=%XzFfQ7)kd^ng5z!WRN7yw{Y1GKhP&;(_wx#IKNM+azaRBMu@D{C~1>|Fj~q;ZwN zxyUSC_PPiHQlgb5qI(IeZTy1NVW69hM0#}uDTuEEA#5)%wtJaX(mY9a$q2E-rM{=) zoY+bdubzo3&kOpnxpAb5GI>u&3xe?G(AR=+x3|Jtlq)|ts=V#xcv;5|2mJ^Sk_5B{DtU`kP}WeqXtQ^U zw5Uy^P>%&r+wixg+8>UbB%2?2-W@B^1_5o!lT}cZ)}we)J_OeSSk;f^=aQ9?G>eM_ z8V?(QPaedcb&wUgZcv2_Ea%jk$CI9((6D@qRFUR3m^RMJAE~nCx|zx^14q?9`7oH^ z-tGp;&Ogk~VR(p?;5(bp$LnZcoyV7F`;hZB1VRB+SUOn)7IX<8z*?1T2+Rf!Pv&fT z%bCq*Fj_PshN_if`NK(zXk8ZVC~6b#nDnIyK%GJYFCiYq4$rD_h}3xY_f~4C!4Eg2 zU4xUc>e>~Z&SOW8=3DTal`V_ISWy{|ZLO`wm$>{IWaVI{gj&$##d_RC?2VK79=sJ# zwiFjB&a?Q%)rYlO6{6iSj#qsUEfh9RC)T&Av~Yb|9awAS9rsnSV28uZ)qLJD3iQ&G z8)c$_NWz1nC>H3+D6-g`7jL+L!VgvM6?wuawNnp*s7l6z9?aLrq57nMOyv`oMtA)e ziR){aS4!Mnm3CY`A3(vjr(>`G+VBUzw~^2C)vN8;cnHafj%8~lW4$1y237RvQ$p?U zKoeWUk`dmAQv5_BNu1RpK1UOCUhu3_*aeYGTlO9OC9w;-tD!D)a|5L}hEDZ7gC>cG zi9|>NC`$!jZ;k6G{q-b~ko@jdne)>PYQC0`C2ewTysBpJ&OMY7OHg<8`JhDT>S@PWQzSo}9pk{8L{c${X+R@~kSYNk}k7Z3SYxgA< zFLaIjttSp3N(LS#o2#WL)ma)aM_4Yv$_#?=BMRqR!umrDT*e#wT4>@%(hGw2LQW ztPV-C6T7~&*XIas?lS%kgu~6(O<5x@k&9d%%PY#UE%;w9PPr}f>b3tQM}WtLk5T{p zluOZM)n){#`4*mP?yF#%y5af0row{}-{0F5ww|!8hfo#*$cBs`fz=t18TR^V4-L6* z2@#~Y(?odH^*(63==EuJ#dxBQ9CtAf&pX(C7biJ^k)g*seGdwjR>4pc$3fYFpg)L$ zjS(_9Lzu6gbU`_f5?b!gL>TEi&bTA%B&Ls%XnsV|x?*$iPr~A>NG{OR^!BT(WVRjV zf|--Z8>>5THRZJAJLS4SzDATSZK-zi1&Ek^jA?ex*C%E>Xt_1~yoWt;mYVymaL)FC z*OF+ahMH?V>paIqZb}`4fRI7{Onjp-iWzSn!jQa*S=5!47fl9zfKniy;lvv1tqM4<b*)d&I`NwuJlLizb_B=^&$qkOZ3O2PSlIjtYyv0RY&bsihI*9PJii-^xL*WPR=M6 zjEbxD&ib1W9H3>(UlKu6@1lplh_%l#HJSF_nEr6~jmUw#FFgD+6dmu#^+?$~_nS=S z{YJuHk65<$HYO=2VNB`}X1o?cOovu8-iU2bqTkVZ)%R!(VB6T>X6{RQ`9vdBE*Olo z5*^DTD;N8D zaC#_!1%Dm!Rg;(Heve4-Wh1BuC!kMRgIA58S_?e`u{nEN`E9BTtrA%yNV%~1iX2)N z{I*D0gzT3w{OyIYXIYDE#BLw>1bG=xf>Dx)4#llS6yr0XKUmc)7 z=f#2YSQF3M9IZ~P+u%uWH+_E|Q&U{Wd-2wojUc=2&2cEc=`AA8-N{i*f8vmNUaw$L z69%m1PW?W7^o~CW>GX_6%h!hl<^)`$nU@8lvDI>of1(n@GHX#ODBlEb!_>a^A`Ach zm#QdQBfr=v{L9eV*>$$$)ttsm%jz1m-~k@XslTOlQ`YO8wBI-P76yt98o*AM4C&A&2`h|wJ zmsR-So@YfHvl%A-jb12spU%dW(pVXSWi@A}l`K`Bd_;td5pn&~Aj2u&Cj3~B>AGAs zoK^^5@_De}1LlBULo#|KgQ{SW-wr{$Hne8aTvfbXK<&EPa zC$3F4x5dhh>~e>zYf?Ha$UG*%7ekC_+Ys+g?v#LX7Dc>(|8*lljbVk zjaNvLZ6Ug~%`9hbcqV2ho6C7l#~*i|&=(+9*btaU;r^}fXC$EI5Yoh^oiUCZC7_n4 zsMjMWX09EhRS(OYVcR_cj@1cqa@b2bn5o7F^NcU&uhVHyHGhTjMnt7e6{n0&aY+f( zrU)$y+-PPFovOUL@@q9==Lo*+MXBopy0uN1evDdp3aci6JHZ{@>*imHlaMtf4A(um zLf=vfy@Obq{v9K4Gsv#?=VdT(?Dy7xm6ASeCTv?7vGhoFm;N6Nk2rZO^ijERLt$%1 z`>-9q%>;}*CHu?J)nn3KUecgSwmt9))0q+3e~T0J+_kXE9>as@Uo>hYM=(l+w8Xle z!h&uJ*b_I367CFke5bxlkX31YOez5CY@02DUu0J7!FMr!mgQ~yxYwIG<3WS;j;{KXlv6SoVI&>1xZ*;{GkAk zV9bkXjYRAFJ@*dGc?b7f8+jx0T+KV&8{%NEdFqlpdxoJRX7IowW}p*X=D9R@#n8#e zEj_)^QsFp^8QHNsqBPH>Ad%cJV`hJFG8G>+%7dYmM~w=`k+WpY{v$&5wFog{L7Uj+ z;@1Cg$9V*INjb-Ykv<}(m804(s}3axywj~nw3xUK9T?q z^I`MUPDHUeqd6G}Bcc;2ouyOfT9lXsS^g<*Z_7JU|jQw&@Bm6i!Dp<-Bh)`6^2Q&_uN5 znq8e?7kxX~B_eEpnlz2u?Fn-tM>=%JZ`1$gkPrNt&uh(9m0&}1Gyiyz*!2BXsVy^T zR}gn+{wv$qPKt!f>I_CCb|K_5WT{#fL*TmgzFwN7LH7|IYyGXXEh)rP+nxswJN{|l z9rNJ7Ry;iTgCeq@(x$?hfGmF62W0IP;>Ke1yB3?!g!Jzc5v)=FtX%)<|q>Q^a5 zT>Ba9MX*1+B^^AVS~wGooV>6V8ur7*cQV^BR1?aw@=34F8H!&kdYKmmh+o)pn99U@ zmQqWE@M&WUfeIV9L5Foaz&Y)xpxTUHYjZjMy~WIc4*r6#*mRTiq^$>NuHorHF3x#`exW=5SA@j0og#H}rQaIxahBAXOz%U3J-==Q1 zW~6Uv$hSu=(6`~{!S_Y*H-!Iyu~G}B9exGDibSK^M$h* zKXectrz*W;oU+tJ+oSDZNn|DPI8IxO@CoM8z{Uc_`GsUXX6nZL^c1EHAxY8if}e#a z+fU%6t9PtG{l3!(U_Qayi)q<|{vON97w%5I%X;d!y4tz6fM{v1P zpFSR@0U@P*+!mL*yJOMSmr90chh$N1i87PSsg(oZD93ECM=Hw2$vYS8oJA=_qG#^U zJ;b_aQ6iD(oFn$GpL#q5bI6A(;nMw%spPeZjwMBCfY)z|i~*xnE(S - - - - -Getting Started - - - - - - - -
    - -Home - | -All Classes - | -Main Classes - | -Annotated - | -Grouped Classes - | -Functions -

    Getting Started

    - - - -[ Home ] -[ Next: Preparing to Migrate the User Interface ] -

    Starting with TQMotif and TQApplication -

    -

    To be able to use TQt, we need to create a TQApplication object. The -TQApplication class controls all the event delivery and display -management for all other TQt objects and widgets. We need to use the -TQMotif class from the TQt Motif Extension to allow TQApplication -and the XtAppContext to coexist. -

    The TQApplication object must be created in the main() function. -We will need to modify todo.c to compile with a C++ compiler, so we -rename todo.c to todo.cpp. -

    Next, we add the appropriate includes for the TQMotif and TQApplication -classes. -

    - -

    
    -

    Next, we create the TQMotif and TQApplication objects. We create TQMotif -with a foreign XtAppContext, and we create TQApplication with a -foreign Display. -

    
    -

    The next change is not yet necessary, but it is included to show that -the TQt Motif Extension provides a complete integration. -Normally, a Motif based program would use the XtAppMainLoop() -function to run the application's event loop. This is still possible, -but since we are migrating to the TQt toolkit, we prefer to use the -TQApplication::exec() function for running the event loop. -

    
    -

    Since we renamed todo.c to todo.cpp, we must change the -project file and rerun qmake to regenerate our Makefile. When we -build our project, there are compile and link errors: we will fix -these in the following section. -

    Migrating to C++ -

    -

    We need to convert the code in this file to proper C++ code. -Fortunately, the changes are not too large. Most files included from -existing C projects are not C++ compatible, so we make them compatible -by wrapping them in an extern "C" block. -

    - -

    
    -

    Global C functions that are forward declared must also be wrapped into -an extern "C" block. -

    
    -

    The manageCB() function needs to be converted to proper C++. -

    
    -

    And we need to fix two invalid casts. One is in the Save() function. -

    
    -

    The other invalid cast is in the Open() function. -

    
    -

    After these changes, the project compiles and links, and the -application runs and operates correctly. -

    [ Home ] -[ Next: Preparing to Migrate the User Interface ] -

    - -


    - -
    Copyright © 2007 -TrolltechTrademarks -
    TQt 3.3.8
    -
    - diff --git a/doc/html/motif-walkthrough-10.html b/doc/html/motif-walkthrough-10.html deleted file mode 100644 index 204c218b..00000000 --- a/doc/html/motif-walkthrough-10.html +++ /dev/null @@ -1,103 +0,0 @@ - - - - - -Continuing Development - - - - - - - -
    - -Home - | -All Classes - | -Main Classes - | -Annotated - | -Grouped Classes - | -Functions -

    Continuing Development

    - - - -[ Previous: Replacing the Print Dialog ] -[ Home ] -

    We have not quite finished with the migration to TQt, even though our -project does not use Motif any more. TQt provides many useful features -that we can begin using immediately. Some of the most interesting -ones are presented below as a guide for where to start extending your -existing projects. -

    Using Unicode -

    -

    Support for internationalization is very easy -with TQt. Using TQString instead of char* for storing text gives -us support for most of the written languages around the world. Our Page and Options structs look much simpler now. -

    - -

    
    -

    
    -

    All functions that use the Page and Options structs need to be -updated to use TQString properly. Since TQString is also an implicitly shared class, we no longer have to do any memory management with our -strings. We can remove all occurences of the tqstrdup() function, -and we never need to use new or delete when done with a string. -TQString will allocate and delete data when needed. -

    Here are the MainWindow::fileOpen() and MainWindow::pageChange() -functions from mainwindow.ui.h. Notice that the code no longer -uses delete or tqstrdup() when storing text. -

    - -

    
    -

    -    ...
    -
    - -

    
    -

    Almost all of the functions in our application are affected by this -change. In most cases, we end up removing more code than we are -adding. To keep the size of this walkthrough reasonable, we've only -shown a small portion of the required changes, since the changes are -very similar to those shown above. -

    Writing Platform-Independent Code -

    -

    TQt provides many input and output classes. We -can use these in MainWindow::readDB() and MainWindow::saveDB(). -Currently, these functions use functions only found on UNIX machines. -Using TQFile and TQTextStream removes this dependency on UNIX, and we can -begin building and testing our application on Microsoft Windows and -Apple Mac OS X. -

    The platform-independent versions of the MainWindow::readDB() and -MainWindow::saveDB() functions can be found in the io.cpp file. -

    Designing a Modern User Interface -

    -

    Since we used the TQt Designer to design the Main Window -widget, we can extend the interface easily. We can use some of the -more advanced features of TQMainWindow, which includes dockable -toolbars. Adding these is simple with the TQt Designer. The -final version of our project includes a toolbar, which provides quick -access to the Open, Save, Print, New Page and Delete to Trash actions. -

    The possibilities are endless. An Edit menu, with the common Cut, Copy and Paste actions, could be added in a relatively -short period of time. -

    [ Previous: Replacing the Print Dialog ] -[ Home ] -

    - -


    - -
    Copyright © 2007 -TrolltechTrademarks -
    TQt 3.3.8
    -
    - diff --git a/doc/html/motif-walkthrough-2.html b/doc/html/motif-walkthrough-2.html deleted file mode 100644 index 6d7c7978..00000000 --- a/doc/html/motif-walkthrough-2.html +++ /dev/null @@ -1,101 +0,0 @@ - - - - - -Preparing to Migrate the User Interface - - - - - - - -
    - -Home - | -All Classes - | -Main Classes - | -Annotated - | -Grouped Classes - | -Functions -

    Preparing to Migrate the User Interface

    - - - -[ Previous: Getting Started ] -[ Home ] -[ Next: Using TQt Standard Dialogs ] -

    We are ready to start migrating the user interface for our project. -As mentioned in the introduction, we do this in steps, ensuring that -our application is still usable at every step of the migration process. -

    The user interface can be viewed as a hierarchy; each top-level window -and dialog depends upon a parent (which is another top-level window or -dialog). When using Motif XmMainWindow widgets, these should be -viewed as two separate entities: the Main Window widget with the -popup-menu hierarchy and the View widget contained in the Main Window widget. The View widget depends on the Main Window -widget. -

    We begin migrating the pieces that have no dependencies, and work our -way up the dependency tree until all the pieces have been migrated. -

    The hierarchy for this project looks something like this: -

    Motif Todo Hierarchy
    -

    We will begin by migrating and replacing all of the dialogs, then the -Main Window widget with popup-menu hierarchy, and finally the View widget. -

    However, we are not ready to begin just yet. The migration process can -be long, but it does not have to be difficult. The Open, Save As, Page Delete and IO Error dialogs use Motif XmFileSelectionBox and XmMessageBox dialogs. TQt provides similar -functionality with TQFileDialog and TQMessageBox, which we can begin -using immediately. -

    The Print dialog is special, however. The Print dialog cannot be -replaced until after we have replaced the View widget. TQt provides -a complete printing mechanism with TQPrinter, but we cannot start using -it until we have replaced the View widget. -

    Removing the Help Dialog -

    -

    The Help dialog is also special. Instead of replacing the Help -dialog with a custom TQDialog, we will use the TQt -Help System classes to provide a more advanced online help. -However, we cannot start using classes like TQToolTip and TQWhatsThis -until we replace the Main Window and View widgets. -

    The help text included with the original project is very small and -only contains information about the XmNoteBook widget. The use of -tooltips and whats-this text will suffice for this example. If your -migration project has a large online help system, we recommend looking -at the Simple HTML Help Browser -example for information on how to build an rich text help system with -hypertext navigation and full printing capabilities, or using TQt Assistant. -

    Removing the existing Help dialog is relatively simple. We remove -the Xmd/Help.h, Xmd/HelpP.h and Xmd/Help.c files from our -project file and regenerate our Makefile. -

    The code to create the Help menu and Help dialog is in todo.cpp. We remove the Xmd/Help.h include, the *help_manager -resource string, the help_cb() function forward declaration and the -help_widget global variable. We also need to remove the code that -creates the Help dialog. We will also remove the code to create -the Help menu, since this menu is now empty. Finally, we remove -the help_cb() function implementation. -

    The Help dialog is now removed from our project. We cannot add -TQToolTip and TQWhatsThis help at the moment, since we are still using -XmMainWindow for the Main Window widget. Once we have -migrated the Main Window and the popup-menu hierarchy, we can -begin using TQToolTip and TQWhatsThis for online help. -

    [ Previous: Getting Started ] -[ Home ] -[ Next: Using TQt Standard Dialogs ] -

    - -


    - -
    Copyright © 2007 -TrolltechTrademarks -
    TQt 3.3.8
    -
    - diff --git a/doc/html/motif-walkthrough-3.html b/doc/html/motif-walkthrough-3.html deleted file mode 100644 index 22b52258..00000000 --- a/doc/html/motif-walkthrough-3.html +++ /dev/null @@ -1,178 +0,0 @@ - - - - - -Using TQt Standard Dialogs - - - - - - - -
    - -Home - | -All Classes - | -Main Classes - | -Annotated - | -Grouped Classes - | -Functions -

    Using TQt Standard Dialogs

    - - - -[ Previous: Preparing to Migrate the User Interface ] -[ Home ] -[ Next: Using Custom TQDialogs ] -

    We start by using two of the TQt Standard -Dialogs: TQFileDialog and TQMessageBox. Both of these classes -provide useful static convenience functions. -

    -
    TQFileDialog::getOpenFileName() replacement for the Open dialog -
    TQFileDialog::getSaveFileName() replacement for the Save As dialog -
    TQMessageBox::information() replacement for Page Delete dialog -
    TQMessageBox::warning() replacement for IO Error dialog. -
    -

    Each of these functions takes a TQWidget *parent argument. If we -pass zero as the parent argument, then we will have dialogs that -are centered on the screen, instead of being centered over our main -window. We can have TQMotifWidget create our XmMainWindow, and we -can then use this class as the parent for both Motif dialogs and TQt -dialogs. -

    We need to include the appropriate headers for TQMotifWidget and -TQFileDialog in todo.cpp. -

    - -

    
    -

    Next, we make a few modifications to how the application is -initialized. We could initialize Xt/Motif and create the XtAppContext ourselves, but TQMotif can do this for us. -We also let TQApplication open the connection to the X server. Next, -we create a TQMotifWidget, passing xmMainWindowWidgetClass as the widgetclass argument. We can now use the TQMotifWidget::motifWidget() -function to access the Motif widget. The shell widget is created -automatically by TQMotifWidget. We use XtParent() to access it. -The top-level window is now a TQMotifWidget, which means we can use it -as the parent for the TQt Standard Dialogs. -

    
    -

    Replacing the Open and Save As Dialogs -

    -

    First, we completely remove all use of the existing Motif file -selection dialog. We remove the Xm/FileSB.h include, the global file_dialog variable, and the code to create the dialog. We also -remove the PresentFDialog() callback function. None of this code -is needed to use TQFileDialog. -

    After removing the PresentFDialog() callback function, we need to -make Open and Save As popup-menu callbacks call the Open() -and Save() functions. -

    First we must change the declaration of these two functions. -

    - -

    
    -

    We also change the arguments to the callbacks. We pass the top-level -TQMotifWidget as the client_data to these functions, since we will -be using it as the parent for the TQFileDialog. -

    
    -

    -    ...
    -
    - -

    
    -

    Next, we modify the Save() function to use -TQFileDialog::getSaveFileName(). -

    
    -

    ... and the Open() function to use TQFileDialog::getOpenFileName(). -

    
    -

    After we build the project, the application runs and operates as -expected. The difference is that the Open and Save As dialogs -now use TQFileDialog. -

    Replacing the Page Delete and IO Error Dialogs -

    -

    The Page Delete dialog is created and used in actions.c. We -need to migrate this file to C++. We rename it to actions.cpp, -modify the project file and regenerate the Makefile. -

    The changes required to make actions.cpp compile are minimal. We -need to wrap more C header files and global variables in an extern "C" block. -

    - -

    
    -

    We need to forward declare the NewPage(), DeletePage(), EditPage() and SaveIt() functions so that the compiler generates -the correct symbols for these functions. -

    
    -

    We need to fix a single invalid pointer cast. -

    
    -

    And we need to change the variable named new to newstr in the Trim() function. -

    We can now change the DeletePage() function to use -TQMessageBox::information(). -

    First, we need to make sure we include the proper header for -TQMessageBox. -

    - -

    
    -

    The code for DeletePage() looks like this: -

    
    -

    At this point in the code, the page should be deleted. The code to do -this is in the DoDeletePage() function. We move the contents of DoDeletePage() to this point and remove the DoDeletePage() function -completely. -

    Next, we change todo.cpp to pass the top-level TQMotifWidget as the -client_data tot he DeletePage() function. -

    - -

    
    -

    The IO Error dialog is created and used in io.c. We need to -migrate this file to C++. We rename it to io.cpp, modify the -project file and regenerate the Makefile. -

    The changes required to make io.cpp compile are minimal. We need -to wrap more C header files and global variables in an extern "C" -block. -

    - -

    
    -

    We need to forward declare the ReadDB() and SaveDB() functions -so that the compiler generates the correct symbols for these -functions. -

    
    -

    The ParseNewLines() function needs to be converted to proper C++. -

    
    -

    The PrintWithNewLines() function also needs to be converted to proper -C++. -

    
    -

    We can now change the ReadDB() and SaveDB() functions to use -TQMessageBox::warning(). -

    First, we need to make sure we include the proper header for TQMessageBox. -

    - -

    
    -

    The code for ReadDB() looks like this: -

    -    ...
    -
    - -

    The code for SaveDB() looks like this: -

    -    ...
    -
    - -

    After we build the project, the application runs and operates as -expected. The difference is that the Page Delete and IO Error dialogs now use TQMessageBox. -

    [ Previous: Preparing to Migrate the User Interface ] -[ Home ] -[ Next: Using Custom TQDialogs ] -

    - -


    - -
    Copyright © 2007 -TrolltechTrademarks -
    TQt 3.3.8
    -
    - diff --git a/doc/html/motif-walkthrough-4.html b/doc/html/motif-walkthrough-4.html deleted file mode 100644 index f5810871..00000000 --- a/doc/html/motif-walkthrough-4.html +++ /dev/null @@ -1,102 +0,0 @@ - - - - - -Using Custom TQDialogs - - - - - - - -
    - -Home - | -All Classes - | -Main Classes - | -Annotated - | -Grouped Classes - | -Functions -

    Using Custom TQDialogs

    - - - -[ Previous: Using TQt Standard Dialogs ] -[ Home ] -[ Next: Using Existing Dialogs with TQMotifDialog ] -

    After we have replaced the standard dialogs, we move onto the custom -dialogs. This project has a single custom dialog: the Page Edit -dialog. -

    Instead of writing the code ourselves, we use TQt Designer to design our dialog. -Designing a custom dialog is beyond the scope of -this document: see the TQt Designer Manual if you're unfamiliar -with TQt's visual design tool. -

    Replacing the Page Edit Dialog -

    -

    The custom TQDialog description for the Page Edit dialog is saved -as pageeditdialog.ui. We add this file to the project file by -adding the line -

    -FORMS = pageeditdialog.ui
    -
    - -to the .pro file, and regenerate the Makefile. The uic -utility generates the code for our custom TQDialog, which is then -compiled and linked into our application. (uic is invoked -automatically from makefiles generated from .pro files.) -

    We need to pass the top-level TQMotifWidget as the client_data -argument to the EditPage function, which we will use as the parent -for our new PageEditDialog. We do this the same way as we have -done for the Open and Save As dialogs in todo.cpp. -

    - -

    
    -

    The EditPage() function is implemented in actions.cpp. We start -by adding the includes needed for the PageEditDialog and TQLineEdit. -

    - -

    
    -

    In the EditPage() function, We create the PageEditDialog, set -the initial values of the three TQLineEdit widgets with values from the -current page and execute the dialog. -

    -    ...
    -
    - -

    At this point in the code, the page properties should be modified. The -code to do this is in the DoEditPage() function. We move the -contents of DoEditPage() to this point and remove the DoEditPage() function completely. -

    The Page struct defined in page.h stores strings in char* -arrays. Since the PageEditDialog and the data it contains will be -destroyed when we return from this function, we need to convert the -unicode TQString data into a TQCString in the local encoding and -duplicate it with tqstrdup(). -

    
    -

    The same process must be done for the minorTab text: -

    
    -

    ... and for the majorTab text: -

    
    -

    [ Previous: Using TQt Standard Dialogs ] -[ Home ] -[ Next: Using Existing Dialogs with TQMotifDialog ] -

    - -


    - -
    Copyright © 2007 -TrolltechTrademarks -
    TQt 3.3.8
    -
    - diff --git a/doc/html/motif-walkthrough-5.html b/doc/html/motif-walkthrough-5.html deleted file mode 100644 index 31b1aebf..00000000 --- a/doc/html/motif-walkthrough-5.html +++ /dev/null @@ -1,109 +0,0 @@ - - - - - -Using Existing Dialogs with TQMotifDialog - - - - - - - -
    - -Home - | -All Classes - | -Main Classes - | -Annotated - | -Grouped Classes - | -Functions -

    Using Existing Dialogs with TQMotifDialog

    - - - -[ Previous: Using Custom TQDialogs ] -[ Home ] -[ Next: Using TQt Main Window Classes ] -

    As mentioned earlier, the Print dialog cannot be replaced until we -have converted the View widget. The Print dialog will be -removed once we have finished our migration, since we will use -TQPrinter instead. Based on this information, we decide that it is not -worth replacing the Print dialog with a custom TQDialog replacement. -Instead, we will keep the Motif based dialog and use TQMotifDialog to -integrate the dialog with the application. -

    Modality Requirements -

    -

    Modality with TQDialog is different from Motif. The TQDialog::exec() -function does not return until the dialog is finished. In Motif, -modality is simply a property of the shell, and the application -programmer must write TQDialog::exec() style functionality if they -want that behavior. -

    Since we will be using TQMotifDialog (which is a TQDialog subclass), we -will need to have an accept and a reject callback for each -dialog we integrate with TQMotifDialog. The predefined Motif dialogs -have these already: the XmNokCallback and XmNcancelCallback -callbacks. However, the Print dialog only has an accept callback -(the XmdNprintCallback), but it does not have a reject callback. -We need to add this. -

    This is easily done. We add an XtCallbackList for the XmNcancelCallback callback in Xmd/PrintP.h: -

    - -

    
    -

    We add the XmNcancelCallback callback to the list of resources for -the XmdPrint widget class in Xmd/Print.c: -

    - -

    
    -

    We need to activate this callback whenever we unmanage the widget and -do not activate the print callback, which is in the do_help_cb() -function: -

    
    -

    ... and in the unmanage_cb() function: -

    
    -

    Integrating the Print Dialog -

    -

    Now that the Print dialog has the appropriate accept and reject callbacks, we can use TQMotifDialog. First we need to include -the TQMotifDialog header in todo.cpp. -

    - -

    
    -

    We add a ShowPrintDialog() function which will create and execute the -print dialog. -

    
    -

    We change the Print menu item callback to call the new ShowPrintDialog() function. We pass the top-level TQMotifWidget, which -we will use as the parent for the dialog. -

    
    -

    The ShowPrintDialog() function creates the Print dialog and -executes it. We use the XmdNprintCallback callback to accept the -dialog and the XmNcancelCallback callback to reject the dialog. We -can do this easily by using the TQMotifDialog::acceptCallback() and -TQMotifDialog::rejectCallback() functions, respectively. We also -ensure that the print callback continues to call the Print() function as before. -

    
    -

    After we build the project, the application runs and operates as -expected. There is no visual or behavioral difference, even though -the Print dialog is using TQMotifDialog. -

    [ Previous: Using Custom TQDialogs ] -[ Home ] -[ Next: Using TQt Main Window Classes ] -

    - -


    - -
    Copyright © 2007 -TrolltechTrademarks -
    TQt 3.3.8
    -
    - diff --git a/doc/html/motif-walkthrough-6.html b/doc/html/motif-walkthrough-6.html deleted file mode 100644 index ba890fa9..00000000 --- a/doc/html/motif-walkthrough-6.html +++ /dev/null @@ -1,129 +0,0 @@ - - - - - -Using TQt Main Window Classes - - - - - - - -
    - -Home - | -All Classes - | -Main Classes - | -Annotated - | -Grouped Classes - | -Functions -

    Using TQt Main Window Classes

    - - - -[ Previous: Using Existing Dialogs with TQMotifDialog ] -[ Home ] -[ Next: Refactoring Existing Code ] -

    After we have replaced all the dialogs, we are ready to begin replacing -the Main Window. As mentioned -above, we will replace the existing XmMainWindow and -popup-menu heirarchy with TQt Main Window -Classes. -

    We will use TQt Designer to design -our new main window. -

    Implementing the Main Window -

    -

    The description for the Main Window is saved as mainwindow.ui. -We add this file to the project file and regenerate the Makefile. -The uic utility generates the code for our Main Window, which -is then compiled and linked into our application. -

    TQt Designer also created the mainwindow.ui.h file. We need to -add the implementation for our Main Window to this skeleton -implementation. -

    We begin by adding the necessary includes for TQApplication -and TQMotifWidget. -

    - -

    
    -

    We need includes for the Motif callback structs and the XmdPrint -widget. -

    
    -

    We are now ready to add implementations for the slots in our Main Window. We have one slot per menu item. Each slot will call the -existing callback functions found in todo.cpp and actions.cpp. -

    -
    File menu -
    New MainWindow::fileNew() calls the New() callback -
    Open MainWindow::fileOpen() calls the Open() callback -
    Save MainWindow::fileSave() calls the SaveIt() callback -
    Save As MainWindow::fileSaveAs() calls the Save() callback -
    Print MainWindow::filePrint() calls the ShowPrintDialog() callback -
    Exit MainWindow::fileExit() calls TQApplication::quit() -
    Selected menu -
    Properties MainWindow::selProperties() calls the EditPage() callback -
    New MainWindow::selNewPage() calls the NewPage() callback -
    Delete to Trash MainWindow::selDeletePage() calls the DeletePage() callback -
    -

    We need to add forward declarations for these callbacks before we can -use them. -

    
    -

    Each of the existing callback functions takes three arguments. We pass -NULL to all of the arguments in this example (with a few exceptions, -see below). The existing code does not rely on any of the arguments. -Each slot implementation is a single line calling the related callback -function. The code is not very interesting and would just take up -space, so we've omitted it. -

    There are four exceptions to the above. The Open(), Save(), EditPage() and DeletePage() callbacks accept a pointer to the -toplevel TQWidget as argument 2 (the client_data argument). For -these four functions, we pass this as the second argument, which is -a toplevel MainWindow derived from TQMainWindow. -

    Replacing the Main Window -

    -

    The next step is to use the new Main Window in our application. -The changes needed in todo.cpp are large due to the large amount of -code being removed. -

    First, we add the include for our new Main Window. -

    - -

    
    -

    We can cleanup the Motif includes, since many of them are no longer -needed. -

    
    -

    The QuitAppl() and manageCB() callbacks are not needed any more, -so we remove them. We do not need the global shell variable -either. We remove it and all references to it in the New(), Save() and Open() callbacks. -

    In main(), we make the large changes. First, we use our new MainWindow instead of TQMotifWidget with XmMainWindow. -

    - -

    
    -

    We will now use TQMotifWidget to create the XmNotebook widget. -

    
    -

    We remove all of the code used to create the Motif menus. The -remaining code in main() is self-explanatory. -

    
    -

    Our application is now using TQMainWindow instead of XmMainWindow. -After we build the project, the application runs and operates as -expected. -

    [ Previous: Using Existing Dialogs with TQMotifDialog ] -[ Home ] -[ Next: Refactoring Existing Code ] -

    - -


    - -
    Copyright © 2007 -TrolltechTrademarks -
    TQt 3.3.8
    -
    - diff --git a/doc/html/motif-walkthrough-7.html b/doc/html/motif-walkthrough-7.html deleted file mode 100644 index 7a3912fe..00000000 --- a/doc/html/motif-walkthrough-7.html +++ /dev/null @@ -1,214 +0,0 @@ - - - - - -Refactoring Existing Code - - - - - - - -
    - -Home - | -All Classes - | -Main Classes - | -Annotated - | -Grouped Classes - | -Functions -

    Refactoring Existing Code

    - - - -[ Previous: Using TQt Main Window Classes ] -[ Home ] -[ Next: Replacing the View Widget ] -

    In the author's view, the existing code is slightly disorganized. -Even though the code does work, some cleanups and reorganization -can only help with readability and maintainability. The steps -described below are not necessary during the migration process but are -included for completeness. -

    Migrating Data Structures to C++ -

    -

    The Page data structure is an opaque data type. The real data -structure is called PageRec; Page defined to be a pointer to a -PageRec. In addition, we have the AllocPage() function that -allocates and initializes memory for a PageRec struct. -

    With C++, we can do this in the constructor. We can also write a -destructor which automatically frees all resources in the PageRec, -instead of having to do it in several different places. -

    The PageRec struct declaration is removed from page.h. We -declare a Page struct with the same data members as PageRec, a -constructor and a destructor. -

    - -

    
    -

    The existing pages, currentPage and maxpages global variables -are removed from the source files. We replace them with extern -declarations in page.h. -

    
    -

    The global variable instantiations are placed in todo.cpp. -

    Each source file contains function declarations that deal with the -global Page related variables. We remove these declarations from -the source files and declare them once in the page.h header file. -

    
    -

    Now that Page has a constructor, we remove the AllocPage() -function. It is no longer needed. The calls to AllocPage() are -replaced with 'new Page()' in the NewPage(), DeletePage() -and ReadDB() functions. We also replace the code to deallocate -pages with delete pages[X], where X is the appropriate index -value. This is done in the ReadDB and DeletePage() functions. -

    Code that accesses the global pages variable does not need to be -modified since the data members of the Page struct did not change. -The existing code will continue to work. -

    The OptionsRec struct declared in page.h is also updated, -following the same pattern as the Page struct above. -

    
    -

    The global variable instantiation is also placed in todo.cpp. -

    Code that accesses the global options variable does not need to be -modified since the data members of the Options struct did not -change. The existing code will continue to work. -

    Using new and delete -

    -

    The destructors of the Page and Options structs use delete -instead of XtFree() to deallocate all char* members. This is a -necessary change since we are migrating away from Xt/Motif. We need -to fix existing code that modifies the Page struct members to use -new and delete ( instead of XtMalloc(), XtNewString() and -XtFree() ). -

    The PageChange() function in todo.cpp simply saves the contents -and cursor position of current page before calling SetPage(). We -use new and delete when modifying members of the Page struct. -

    - -

    
    -

    When storing the context of the XmText widget, we use tqstrdup() -to make a copy of the string returned by the XmTextGetString() -function. -

    
    -

    The ReadDB() function in io.cpp needs similar changes. We -replace all use of XtMalloc() and XtNewString() with new and -tqstrdup(), respectively. -

    This needs to be done just after opening the file. -

    - -

    
    -

    ... when starting a new page ... -

    -    ...
    -
    - -
    
    -

    ... and when reading in the label and tab texts/ -

    -    ...
    -
    - -
    -    ...
    -
    - -
    -    ...
    -
    - -
    
    -

    The ReadDB() function uses XtRealloc() to expand the data -storage buffer. Unfortunately, C++ does not provide a way to -reallocate an existing block of data, so we have to do this ourselves. -

    
    -

    There is also one occurence in ReadDB() where we call XtMalloc() -with an argument of 2. This was done when a file could not be read. -Creating an empty string is not necessary, so we remove this code -instead of using new. -

    
    -

    The SaveDB() function in io.cpp also needs these changes. We -change one occurence of XtFree() to delete. -

    
    -

    Finally, We need to replace two occurences of XtNewString() in the main() function in todo.cpp. -

    - -

    
    -

    Moving Existing Code -

    -

    The rest of the refactoring process involves moving existing code into -new places. Currently, each function in the mainwindow.ui.h file -simply calls the old callback handlers present in the other files. -Instead of calling the old callback functions, the implementations are -moved accordingly. -

    -
    Function Original File Moved to Function -
    New() todo.cpp MainWindow::fileNew() -
    Open() todo.cpp MainWindow::fileOpen() -
    SaveIt() actions.cpp MainWindow::fileSave() -
    Save() todo.cpp MainWindow::fileSaveAs() -
    ShowPrintDialog() todo.cpp MainWindow::filePrint() -
    EditPage() actions.cpp MainWindow::selProperties() -
    NewPage() actions.cpp MainWindow::selNewPage() -
    DeletePage() actions.cpp MainWindow::selDeletePage() -
    -

    The Print() callback function is still used by the Print -dialog, so we move it into mainwindow.ui.h and make it static. -

    Previously, the Open(), Save(), EditPage() and DeletePage() -functions created dialogs with client_data as the parent argument. -Since we have moved the code directly into the Main Window -implementation, we create these dialogs with this as the parent -argument. -

    The PageChange() callback function is moved from actions.cpp -to todo.cpp and made static since it is not used anywhere else. -

    Earlier modifications to actions.cpp caused the Trim() function -to become redundant, so we remove it. -

    The MIN() and MAX() macros in todo.cpp are redundant. TQt -provides the TQMIN() and TQMAX() macros which we will use. -

    Earlier modifications caused the fallback_resources array to become -redundant, so we remove it. -

    In the near future, our program will not use Motif any more, and we -will no longer need to use TQMotif. To prepare for this, we remove the -resources and optionDesc arrays and create the TQMotif instance -with just the APP_CLASS argument. -

    The #include statements in the source files are mostly incorrect -due to the refactoring changes. Many of the #include statements -are no longer needed. The #include statements from each file are -listed below, instead of describing which includes are removed and -added to each file. -

    Includes for actions.cpp: -

    - -

    
    -

    Includes for io.cpp: -

    - -

    
    -

    Includes for todo.cpp: -

    - -

    
    -

    Includes for mainwindow.ui.h: -

    - -

    
    -

    [ Previous: Using TQt Main Window Classes ] -[ Home ] -[ Next: Replacing the View Widget ] -

    - -


    - -
    Copyright © 2007 -TrolltechTrademarks -
    TQt 3.3.8
    -
    - diff --git a/doc/html/motif-walkthrough-8.html b/doc/html/motif-walkthrough-8.html deleted file mode 100644 index 15c54a2b..00000000 --- a/doc/html/motif-walkthrough-8.html +++ /dev/null @@ -1,212 +0,0 @@ - - - - - -Replacing the View Widget - - - - - - - -
    - -Home - | -All Classes - | -Main Classes - | -Annotated - | -Grouped Classes - | -Functions -

    Replacing the View Widget

    - - - -[ Previous: Refactoring Existing Code ] -[ Home ] -[ Next: Replacing the Print Dialog ] -

    We are ready to start replacing the View widget. However, our -example program uses the XmNotebook widget class. TQt does not -provide a direct equivalent of this class, so we are faced with three -possibilities, each with several advantages and disadvantages. -

      -

    1. We can continue the conversion using existing TQt widgets. -

        -

      • Advantages - The widgets provided by TQt are well designed and -tested, allowing us to quickly redesign the user interface. -

      • Disadvantages - Most, if not all, of the existing data structures -and code will need to be modified or rewritten. New code must be -written in a way that maintains compatibility with previous versions -of our application. -

      -

    2. We can write a new TQWidget subclass that is identical to the XmNotebook widget class. -

        -

      • Advantages - The existing data structures will not change, allowing -compatibility with previous and future versions. -

      • Disadvantages - The new widget will need to be written and -regression tested. Existing code in our application will need to be -changed in order to deal with the new widget's API. -

      -

    3. We can leave the XmNotebook widget untouched. -

        -

      • Advantages - The existing data structures and code remain -unchanged, allowing us to continue development on other projects, -new features, etc. -

      • Disadvantages - This is the simplest solution, but the application -will still be dependent upon X11; we will not be able to deploy our -application on all platforms supported by TQt. -

      -

    -

    We will use the first approach to complete the migration of the -example project used in this walkthrough, using TQTextEdit, TQLabel and -TQSpinBox to provide a similar look. The only difference is that we -will not have tabs. -

    We use TQt Designer to add the -TQTextEdit, TQLabel and TQSpinBox widgets to the Main Window widget. -

    Data Structure Modifications -

    -

    The Page struct contains majorPB and minorPB members which -need to be removed.  These members correspond to the tabs displayed in -the existing version. The new version will not have any tabs, so we -remove them. -

    - -

    
    -

    Code Modifications -

    -

    Most of the existing functions in our application need to be modified -to work with the new View widget. The MainWindow class has five -new functions that correspond to existing functions. -

    -
    Existing Function New Function -
    void SetPage( int ) void MainWindow::setPage( int ) -
    void PageChange( ... ) void MainWnidow::pageChange( int ) -
    void TextChanged( ... ) void MainWnidow::textChanged() -
    void ReadDB( char * ) void MainWindow::readDB( char * ) -
    void SaveDB( char * ) void MainWindow::saveDB( char * ) -
    -

    -

    The SetPage() function implementation is moved to the MainWindow::setPage() function in mainwindow.ui.h. We remove the -SetPage() function declaration and implementation from page.h -and actions.cpp, respectively. In order to make MainWindow::setPage() work correctly, we need to modify the code to -use the new widgets in our Main Window widget. -

    - -

    
    -

    First, we set the current value of the spinbox to the current page -number. -

    
    -

    Next, we set the current text and cursor position of the textedit -to the contents of the current page. -

    
    -

    If the current page has a custom label, we set it as the current text -of the textlabel; otherwise we set the textlabel contents to -"Page X" (where X is the current page number). -

    
    -

    If the current page has major and/or minor tab text, we append these -to the labeltext. This ensures that all information entered by the -user remains visible. -

    
    -

    We should continue to handle the possibility that the current page -does not exist. In this case, we clear the contents of the textedit widget and set the textlabel contents to the current page -number (with an indication that the page is invalid). -

    
    -

    The PageChange() function is moved from todo.cpp to the MainWindow::pageChange() function in mainwindow.ui.h. As with the -MainWindow::setPae() function, we need to modify the code to use -the new widgets in our Main Window widget. -

    Note: TQTextEdit::text() returns a TQString, which needs to be converted -into a normal char* array. To do this we create a copy of the -string in the local encoding. We need to make the copy using tqstrdup() because the data contained in the TQCString returned by -TQString::local8Bit() is deallocated when the TQCString is destroyed. -

    
    -

    The TextChanged() function does nothing more than set the modified variable to 1. Our new MainWindow::textChanged() function -does exactly the same. -

    
    -

    Since both the MainWindow::pageChange() and MainWindow::textChanged() functions access the modified global -variable, we add a forward declaration at the top of mainwindow.ui.h. -

    -

    The ReadDB() and \s SaveDB() implementations in io.cpp are -renamed to MainWindow::readDB() and MainWindow::saveDB(), -respectively. We need to modify the code in order to make the code -work properly. -

    First, We add #include statements for the MainWindow, TQSpinBox -and TQTextEdit classes. -

    - -

    
    -

    The new MainWindow::readDB() and MainWindow::saveDB() functions -will not use any Xt/Motif functions, so we remove the Xt/Motif #include statements and the global variables notebook and textw. -These functions remain largely unchanged, maintaining compatibility -with previous versions. Also, the ReadDB() and SaveDB() -functions have been converted into MainWindow member functions, so -we can pass this as the parent argument to the TQMessageBox -functions. -

    
    -

    After reading the file in the MainWindow::readDB() function, we set -the current and maximum values of the spinbox to the appropriate -values. -

    - -

    
    -

    In the MainWindow::saveDB() function, we need to store the text -currently displayed, so we use TQTextEdit::text() instead of XmTextGetString(). Note: TQTextEdit::text() returns a TQString, which -needs to be converted into a normal char* array. To do this we -create a copy of the string in the local encoding. We need to make -the copy using tqstrdup() because the data contained in the TQCString -returned by TQString::local8Bit() is deallocated when the TQCString is -destroyed. -

    
    -

    -

    Due to the removal of the majorPB and minorPB members from the -Page struct, the FixPages() function in actions.cpp is no -longer needed. We remove the implementation and forward declaration -of FixPages() from actions.cpp and page.h, respectively. -Calls to FixPages() are removed from the MainWindow::selNewPage() and MainWindow::selDeletePage(), both of -which are in mainwindow.ui.h. -

    We move AdjustPages() to mainwindow.ui.h and make it static, -since it is only used in this file. We remove the forward declaration -from page.h as well. -

    After our modifications, the actions.cpp file is empty. We remove -it from our project file and regenerate our Makefile. -

    -

    Now that we have implemented our new View widget, we need to remove -the old Motif based view widget from todo.cpp. -

    Since we will not be using any Motif widgets, we remove all Motif #include statements, including tqmotifwidget.h. -

    - -

    
    -

    We also remove the forward declarations of the ReadDB() function -and the notebook, textw and labelw global variables. -

    
    -

    Next, we remove the center widget, which uses TQMotifWidget. The Main Window widget and View widget are contained entirely in our -MainWindow class, so no extra initialization is needed after -creating the mainwindow widget. -

    
    -

    Since the ReadDB() and SetPage() functions have been changed into -MainWindow member functions, we need to call them using our mainwindow instance. -

    
    -

    The View widget has now been replaced. After building our project, -we confirm that the application works correctly. -

    [ Previous: Refactoring Existing Code ] -[ Home ] -[ Next: Replacing the Print Dialog ] -

    - -


    - -
    Copyright © 2007 -TrolltechTrademarks -
    TQt 3.3.8
    -
    - diff --git a/doc/html/motif-walkthrough-9.html b/doc/html/motif-walkthrough-9.html deleted file mode 100644 index 8d21cd1c..00000000 --- a/doc/html/motif-walkthrough-9.html +++ /dev/null @@ -1,104 +0,0 @@ - - - - - -Replacing the Print Dialog - - - - - - - -
    - -Home - | -All Classes - | -Main Classes - | -Annotated - | -Grouped Classes - | -Functions -

    Replacing the Print Dialog

    - - - -[ Previous: Replacing the View Widget ] -[ Home ] -[ Next: Continuing Development ] -

    The Print dialog is the last component in our application that -uses Motif. The current Print() function does nothing more than -write the plain text to a temporary file, and then executes 'lpr' to -send the text to the printer. Since we will use TQPrinter, we do not -this function any more, so we remove it. The current MainWindow::filePrint() implementation is removed as well. We will -write a new MainWindow::filePrint() implementation in mainwindow.ui.h. -

    Note: The steps involved in using the TQPrinter class are beyond the -scope of this walkthrough and will not be discussed here. The -TQPrinter Class Reference, TQSimpleRichText Class Reference and the -Simple Application Walkthrough -contain information on the use of TQPrinter. -

    For completeness, the code to initialize a TQPrinter object is included below. -

    - -

    
    -

    Using Rich Text for Printing -

    -

    TQt provides rich text using a subset of HTML. The TQSimpleRichText -class makes rich-text printing simple. All we need to do is create a -string with the proper format tags inserted at the appropriate -places. For our example, we will keep the printing output similar to -previous versions. -

    First, we create the format tags that we will use. -

    
    -

    Next we just loop over all pages, appending the page label, contents -and formatting characters to a printtext variable (which is a -TQString). -

    
    -

    The rest of the MainWindow::filePrint() function is the actual -printing code. Here we simply create a TQSimpleRichText object using -the string we created above, and draw this string on the TQPrinter -object using TQPainter. -

    
    -

    Removing the Dependency on Xt/Motif -

    -

    Our application no longer uses any Xt or Motif widgets. We can now -finish removing the dependencies on Xt and Motif. -

    First, we cleanup the #include statements in mainwindow.ui.h. -

    - -

    
    -

    The MainWindow::fileNew() function uses the Boolean and False -keywords from the Xt library. C++ has these built into the language, -so we use bool and false instead. -

    The last modification needed to completely remove Xt and Motif from -our application is to stop using the TQMotif class. We remove the -tqmotif.h #include statement from todo.cpp, and remove the -instantiation from the main() function. -

    After doing this, we can remove the -lXm and -lqmotif from the -LIBS variable in our project file. Our project file also contains -source and headers for the the old custom Motif widgets previously -used in our application. We remove these as well. -

    After regenerating the Makefile and building our project, we -confirm that the application works correctly. -

    [ Previous: Replacing the View Widget ] -[ Home ] -[ Next: Continuing Development ] -

    - -


    - -
    Copyright © 2007 -TrolltechTrademarks -
    TQt 3.3.8
    -
    - diff --git a/doc/html/motif-walkthrough.html b/doc/html/motif-walkthrough.html deleted file mode 100644 index 1c52bd6e..00000000 --- a/doc/html/motif-walkthrough.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - -TQt Motif Extension - A Migration Walkthrough - - - - - - - -
    - -Home - | -All Classes - | -Main Classes - | -Annotated - | -Grouped Classes - | -Functions -

    TQt Motif Extension - A Migration Walkthrough

    - - - -[ Next: Getting Started ] -

    This walkthrough covers a complete migration of a Motif based program -to the TQt toolkit using the TQt Motif Extension. -

    It is rarely practical for a large project with hundreds of thousands -or even millions of lines of code to be migrated all at once; such an -endeavor would require too many development resources and would incur -significant risks. Every line of code would have to be rewritten, -every user interface redesigned, and quality assurance tests and -procedures all rewritten. The TQt Motif Extension provides a -complete and working solution for incremental migration that can be -paced to suit each individual project and the available resources. The -user interface and related code can be migrated in steps while the -rest of the project need not be changed at all. -

    This walkthrough is intended for programmers who will be migrating an -existing Motif based project to the TQt toolkit. We assume that they -have experience with C/C++ and Xt/Motif. Some experience with the TQt -toolkit is also necessary. For developers completely new to TQt we -recommend following the learning plan outlined in How to Learn TQt; or to go on a TQt -training course. (See http://www.trolltech.com for -details of training courses.) -

    Goals for the Walkthrough -

    -

    The goal of this walkthrough is to provide the reader with enough -knowledge to migrate Motif applications to the TQt toolkit. We will do -this by example: We will convert a real-world Motif based program -step-by-step. This walkthrough will discuss both techniques and their -rationales throughout the process. This walkthrough is broken down -into individual chapters which cover a specific topic: -

    -

    We will use the todo demo program included with the Motif 2.x -distribution as our migration project. This walkthrough contains -references to the source code, which is included in the extensions/motif/examples/walkthrough subdirectory. -

    Prerequisites -

    -

    Before we can start using the TQt Motif Extension, we must satisfy -these requirements: -

      -
    1. We are using the X11R6.x and Motif 2.x libraries. -
    2. The project is compilable by a C++ compiler. -
    3. We have built and installed the TQt Motif Extension. -
    4. We have built and linked the project with the TQt toolkit and the TQt Motif Extension -
    -

    X11R6.x and Motif 2.x Libraries -

    -

    The mechanisms used by the TQt Motif Extension require development -headers and libraries from the X11R6 release and the Motif 2.0 -release. Newer versions of these can also be used. -

    C++ Compiler -

    -

    Since TQt is a C++ toolkit, all new code will be written in C++. In -order for existing code to coexist with new code, a C++ compiler must -be able to compile the existing code. -

    It is possible to keep existing code and new code separate, and only -convert or rewrite existing code as needed. This is a normal part -of the migration process, and does not need to be done before the -migration process begins. This is the most common scenario, and we -will demonstrate it by migrating existing C code to C++ as needed in -this walkthrough. -

    Build and Install the TQt Motif Extension -

    -

    The TQt Motif Extension is not built and installed along with the -TQt toolkit. The extension resides in the extensions/motif -subdirectory. Run make in this directory to build the extension -and the examples. Once the extension has been built, run make install. -

    -    $ cd extensions/motif
    -    $ make
    -    $ make install
    -
    - -

    The TQt Motif Extension is now installed and ready to use. -

    Build and Link the Project with the TQt Toolkit and the TQt Motif Extension -

    -

    For simplicity, we use qmake to create the Makefile. The -project option causes qmake to automatically generate a project -file. After qmake -project has generated our project file, we -run qmake again to generate a Makefile. Now, we can just run make to build our project. -

    -    $ qmake -project
    -    $ qmake
    -    $ make
    -
    - -

    Everything builds correctly, but fails to link because we don't link -with the Motif library. We tell qmake to do this by adding the -lXm to the LIBS variable in our project file. Since we are -planning to use the TQt Motif Extension in this project as well, -we should also add -lqmotif to the list of libraries. -

    -    LIBS += -lXm -lqmotif
    -
    - -

    Now we regenerate our Makefile by running qmake again, and -rebuild using make. This time, our project successfully links, and -the application runs as expected. -

    We are now ready to start using the TQt Motif Extension. -

    [ Next: Getting Started ] -

    - -


    - -
    Copyright © 2007 -TrolltechTrademarks -
    TQt 3.3.8
    -
    - diff --git a/doc/html/opengl.html b/doc/html/opengl.html index 7b6e4f3c..3fce7175 100644 --- a/doc/html/opengl.html +++ b/doc/html/opengl.html @@ -40,7 +40,7 @@ body { background: #ffffff; color: black; }

    OpenGL only deals with 3D rendering and provides little or no support for GUI programming issues. The user interface for an OpenGL* application must be created with another toolkit, -such as Motif on the X platform, Microsoft Foundation Classes (MFC) +such as Motif on the X platform, Microsoft Foundation Classes (MFC) under Windows, or TQt on both platforms.

    The TQt OpenGL module makes it easy to use OpenGL in TQt applications. It provides an OpenGL widget class that can be used just like any diff --git a/doc/html/overviews-list.html b/doc/html/overviews-list.html index b004d787..54235555 100644 --- a/doc/html/overviews-list.html +++ b/doc/html/overviews-list.html @@ -77,7 +77,6 @@ body { background: #ffffff; color: black; }

  • Events and Event Filters
  • Keyboard Focus Overview
  • Standard Accelerators -
  • Motif Support Extension
  • OpenGL Overlays (X11)
  • Setting the Application Icon
  • Session Management diff --git a/doc/html/pictures.html b/doc/html/pictures.html index 75f42bb0..23b8a6de 100644 --- a/doc/html/pictures.html +++ b/doc/html/pictures.html @@ -33,7 +33,7 @@ body { background: #ffffff; color: black; } -

    Most of these widgets are shown in either Motif or Windows style. +

    Most of these widgets are shown in either Motif or Windows style. All widgets are supported in both styles (and other styles), but for clarity we just present a selection.

    TQt provides more widgets than the selection shown below. And extra TQt are available from third parties, and as add-ons to TQt; see TQt diff --git a/doc/html/propertydocs b/doc/html/propertydocs index a4862209..83d70b6d 100644 --- a/doc/html/propertydocs +++ b/doc/html/propertydocs @@ -424,7 +424,7 @@ setting. <p>This property holds whether the combobox is editable. <p>This property's default is FALSE. Note that the combobox will be -cleared if this property is set to TRUE for a 1.x <a href="motif-extension.html#Motif">Motif</a> style +cleared if this property is set to TRUE for a 1.x Motif style combobox. To avoid this, use <a href="tqcombobox.html#setEditable">setEditable</a>() before inserting any items. Also note that the 1.x version of Motif didn't have any editable comboboxes, so the combobox will change it's appearance @@ -454,7 +454,7 @@ to a 2.0 style Motif combobox is it is set to be editable. TQComboBox::sizeLimit <p>This property holds the maximum on-screen size of the combobox. -<p>This property is ignored for both <a href="motif-extension.html#Motif">Motif</a> 1.x style and non-editable +<p>This property is ignored for both Motif 1.x style and non-editable comboboxes in Mac style. The default limit is ten lines. If the number of items in the combobox is or grows larger than lines, a scrollbar is added. @@ -2435,7 +2435,7 @@ undefined. <p>This property holds whether the list view shows open/close signs on root items. <p>Open/close signs are small <b>+</b> or <b>-</b> symbols in windows -style, or arrows in <a href="motif-extension.html#Motif">Motif</a> style. The default is FALSE. +style, or arrows in Motif style. The default is FALSE. <p>Set this property's value with <a href="tqlistview.html#setRootIsDecorated">setRootIsDecorated</a>() and get this property's value with <a href="tqlistview.html#rootIsDecorated">rootIsDecorated</a>(). @@ -2616,7 +2616,7 @@ property. The default icon is TQMessageBox::NoIcon. <p>This property holds the current icon. <p>The icon currently used by the message box. Note that it's often -hard to draw one pixmap that looks appropriate in both <a href="motif-extension.html#Motif">Motif</a> and +hard to draw one pixmap that looks appropriate in both Motif and Windows GUI styles; you may want to draw two pixmaps. <p> <p>See also <a href="tqmessagebox.html#icon-prop">icon</a>. diff --git a/doc/html/qt.dcf b/doc/html/qt.dcf index 65d02114..0c680c35 100644 --- a/doc/html/qt.dcf +++ b/doc/html/qt.dcf @@ -4701,24 +4701,6 @@

    -
    - TQMotif - applicationContext - x11Display - ~TQMotif -
    -
    -
    -
    - TQMotifDialog - acceptCallback - dialog - rejectCallback - shell - ~TQMotifDialog -
    -
    -
    TQMotifPlusStyle
    @@ -4731,13 +4713,6 @@
    -
    - TQMotifWidget - motifWidget - ~TQMotifWidget -
    -
    -
    TQMouseEvent accept @@ -9164,15 +9139,6 @@
    -
    - isActiveWindow - setActiveWindow - x11Event - xtWidget - ~QXtWidget -
    -
    -
    3rd Party Licenses used in Qt
    @@ -9188,9 +9154,6 @@
    A Directory Browser
    -
    - A Motif Dialog -
    A qt-interest mail archive search
    @@ -9299,9 +9262,6 @@
    Connect the Points
    -
    - Continuing Development -
    Conway's Game of Life
    @@ -9368,9 +9328,6 @@
    Format of the TQDataStream Operators
    -
    - Getting Started -
    GNU General Public License
    @@ -9557,9 +9514,6 @@
    Porting to TQt 3.x
    -
    - Preparing to Migrate the User Interface -
    Presenting the GUI
    @@ -9587,9 +9541,6 @@
    QMag
    -
    - motif-examples -
    tqprocess-examples
    @@ -9605,12 +9556,6 @@
    TQt Editions
    -
    - TQt Motif Extension -
    -
    - TQt Motif Extension - A Migration Walkthrough -
    TQt Object Model
    @@ -9704,15 +9649,6 @@
    Range controls
    -
    - Refactoring Existing Code -
    -
    - Replacing the Print Dialog -
    -
    - Replacing the View Widget -
    Richtext
    @@ -9863,27 +9799,12 @@
    User Interface Compiler (uic)
    -
    - Using Custom TQDialogs -
    -
    - Using Existing Dialogs with TQMotifDialog -
    Using menus
    -
    - Using TQt Main Window Classes -
    -
    - Using TQt Standard Dialogs -
    Using the Meta Object Compiler
    -
    - Using the Motif Event Loop -
    Walkthrough: A Simple Application
    diff --git a/doc/html/qxtwidget-h.html b/doc/html/qxtwidget-h.html deleted file mode 100644 index d8cde310..00000000 --- a/doc/html/qxtwidget-h.html +++ /dev/null @@ -1,110 +0,0 @@ - - - - - -qxtwidget.h Include File - - - - - - - -
    - -Home - | -All Classes - | -Main Classes - | -Annotated - | -Grouped Classes - | -Functions -

    qxtwidget.h

    - -

    This is the verbatim text of the qxtwidget.h include file. It is provided only for illustration; the copyright remains with Trolltech. -


    -
    -/****************************************************************************
    -** $Id: qt/qxtwidget.h   3.3.8   edited Jan 11 14:37 $
    -**
    -** Definition of TQt extension classes for Xt/Motif support.
    -**
    -** Copyright (C) 1992-2007 Trolltech ASA.  All rights reserved.
    -**
    -** This file is part of the TQt extension for Xt/Motif support.
    -**
    -** Licensees holding valid TQt Enterprise Edition licenses for X11 may use
    -** this file in accordance with the TQt Commercial License Agreement provided
    -** with the Software.
    -**
    -** This file is not available for use under any other license without
    -** express written permission from the copyright holder.
    -**
    -** This file is provided AS IS with NO WARRANTY OF ANY KIND, INCLUDING THE
    -** WARRANTY OF DESIGN, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
    -**
    -** See http://www.trolltech.com/pricing.html or email sales@trolltech.com for
    -**   information about TQt Commercial License Agreements.
    -**
    -** Contact info@trolltech.com if any conditions of this licensing are
    -** not clear to you.
    -**
    -**********************************************************************/
    -
    -#ifndef TQXTWIDGET_H
    -#define TQXTWIDGET_H
    -
    -#include <tqwidget.h>
    -
    -#include <X11/Intrinsic.h>
    -
    -
    -class TQXtWidget : public TQWidget {
    -    TQ_OBJECT
    -    Widget xtw;
    -    Widget xtparent;
    -    bool   need_reroot;
    -    void init(const char* name, WidgetClass widget_class,
    -	      Widget parent, TQWidget* qparent,
    -	      ArgList args, Cardinal num_args,
    -	      bool managed);
    -    friend void tqwidget_realize( Widget widget, XtValueMask* mask,
    -				 XSetWindowAttributes* attributes );
    -
    -public:
    -    TQXtWidget(const char* name, Widget parent, bool managed=FALSE);
    -    TQXtWidget(const char* name, WidgetClass widget_class,
    -	      TQWidget *parent=0, ArgList args=0, Cardinal num_args=0,
    -	      bool managed=FALSE);
    -    ~TQXtWidget();
    -
    -    Widget xtWidget() const { return xtw; }
    -    bool isActiveWindow() const;
    -    void setActiveWindow();
    -
    -protected:
    -    void moveEvent( TQMoveEvent* );
    -    void resizeEvent( TQResizeEvent* );
    -    bool x11Event( XEvent * );
    -};
    -
    -#endif // TQXTWIDGET_H
    -
    - -


    - -
    Copyright © 2007 -TrolltechTrademarks -
    TQt 3.3.8
    -
    - diff --git a/doc/html/qxtwidget-members.html b/doc/html/qxtwidget-members.html deleted file mode 100644 index 1612ab73..00000000 --- a/doc/html/qxtwidget-members.html +++ /dev/null @@ -1,338 +0,0 @@ - - - - - -TQXtWidget Member List - - - - - - - -
    - -Home - | -All Classes - | -Main Classes - | -Annotated - | -Grouped Classes - | -Functions -

    Complete Member List for TQXtWidget

    - -

    This is the complete list of member functions for -TQXtWidget, including inherited members. - -

    - -


    - -
    Copyright © 2007 -TrolltechTrademarks -
    TQt 3.3.8
    -
    - diff --git a/doc/html/qxtwidget.html b/doc/html/qxtwidget.html deleted file mode 100644 index 84560800..00000000 --- a/doc/html/qxtwidget.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - -TQXtWidget Class - - - - - - - -
    - -Home - | -All Classes - | -Main Classes - | -Annotated - | -Grouped Classes - | -Functions -

    TQXtWidget Class Reference
    [obsolete]

    - -

    The TQXtWidget class allows mixing of Xt/Motif and TQt widgets. -This class is obsolete. It is provided to keep old source working. We strongly advise against using it in new code. -More... -

    This class is part of the TQt Motif Extension. -

    #include <qxtwidget.h> -

    Inherits TQWidget. -

    List of all member functions. -

    Public Members

    - -

    Protected Members

    -
      -
    • virtual bool x11Event ( XEvent * e )
    • -
    -

    Detailed Description

    -

    This class is defined in the TQt Motif Extension, which can be found in the qt/extensions directory. It is not included in the main TQt API. -

    - -The TQXtWidget class allows mixing of Xt/Motif and TQt widgets. -This class is obsolete. It is provided to keep old source working. We strongly advise against using it in new code. -

    -

    TQXtWidget acts as a bridge between Xt and TQt. For utilizing old Xt -widgets, it can be a TQWidget based on a Xt widget class. For -including TQt widgets in an existing Xt/Motif application, it can be -a special Xt widget class that is a TQWidget. See the constructors -for the different behaviors. -

    Known TQXtWidget Problems -

    -

    This class is unsupported and has many known problems and -limitations. It is provided only to keep existing source working; -it should not be used in new code. Note: These problems will not -be fixed in future releases. -

    Below is an imcomplete list of know issues: -

      -

    1. Keyboard focus navigation is impossible when using TQXtWidget. -The mouse must be used to focus widgets in both TQt and Xt/Motif -widgets. For example, when embedding a TQXtWidget into an Xt/Motif -widget, key events will go to the TQXtWidget (and its children) while -the mouse is over the TQXtWidget, regardless of where Xt/Motif has -placed the focus. -

    2. Reparenting does not work. You cannot use -TQWidget::reparent(). This includes the functions -TQWidget::showFullScreen() and TQWidget::showNormal(), which use -TQWidget::reparent(). -

    - -

    Member Function Documentation

    -

    TQXtWidget::TQXtWidget ( const char * name, Widget parent, bool managed = FALSE ) -

    -Constructs a TQXtWidget of the special Xt widget class known as -"TQWidget" to the resource manager. -

    Use this constructor to utilize TQt widgets in an Xt/Motif -application. The TQXtWidget is a TQWidget, so you can create -subwidgets, layouts, etc. using TQt functionality. -

    The name is the object name passed to the TQWidget constructor. -The widget's parent is parent. -

    If the managed parameter is TRUE and parent in not null, -XtManageChild it used to manage the child. - -

    TQXtWidget::TQXtWidget ( const char * name, WidgetClass widget_class, TQWidget * parent = 0, ArgList args = 0, Cardinal num_args = 0, bool managed = FALSE ) -

    -Constructs a TQXtWidget of the given widget_class called name. -

    Use this constructor to utilize Xt or Motif widgets in a TQt -application. The TQXtWidget looks and behaves -like the Xt class, but can be used like any TQWidget. -

    Note that Xt requires that the most top level Xt widget is a shell. -This means, if parent is a TQXtWidget, the widget_class can be -of any kind. If there isn't a parent or the parent is just a normal -TQWidget, widget_class should be something like topLevelShellWidgetClass. -

    The arguments, args, num_args are passed on to XtCreateWidget. -

    If the managed parameter is TRUE and parent in not null, -XtManageChild it used to manage the child. - -

    TQXtWidget::~TQXtWidget () -

    -Destructs the TQXtWidget. - -

    bool TQXtWidget::isActiveWindow () const -

    -Different from TQWidget::isActiveWindow() - -

    void TQXtWidget::setActiveWindow () [virtual] -

    -Implement a degree of focus handling for Xt widgets. - -

    Reimplemented from TQWidget. -

    bool TQXtWidget::x11Event ( XEvent * e ) [virtual protected] -

    -Reimplemented to produce the Xt effect of getting focus when the -mouse enters the widget. The event is passed in e. - -

    Reimplemented from TQWidget. -

    Widget TQXtWidget::xtWidget () const -

    - -

    Returns the Xt widget equivalent for the TQt widget. - - -


    -This file is part of the TQt toolkit. -Copyright © 1995-2007 -Trolltech. All Rights Reserved.


    - -
    Copyright © 2007 -TrolltechTrademarks -
    TQt 3.3.8
    -
    - diff --git a/doc/html/titleindex b/doc/html/titleindex index 8b76d462..10380c1b 100644 --- a/doc/html/titleindex +++ b/doc/html/titleindex @@ -3,7 +3,6 @@ A Complete Application Window | simple-application-example.html A Complete Application Window with Actions | tqaction-application-example.html A Complete Canvas Application | canvas-chart-example.html A Directory Browser | dirview-example.html -A Motif Dialog | motif-dialog-example.html A Rectangle Draw "Benchmark" | forever-example.html A Small Application for Testing Regular Expressions | regexptester-example.html A Tiny Example Featuring a Toggle Action | toggleaction-example.html @@ -40,7 +39,6 @@ Class Inheritance Hierarchy | hierarchy.html Collection Classes | collection.html Company Information | troll.html Connect the Points | drawlines-example.html -Continuing Development | motif-walkthrough-10.html Conway's Game of Life | life-example.html Cursors | cursor-example.html Customized Layoutmanager | customlayout-example.html @@ -64,7 +62,6 @@ File Handling | tutorial2-07.html Font Displayer | qfd-example.html Format of the TQDataStream Operators | datastreamformat.html GNU General Public License | gpl.html -Getting Started | motif-walkthrough-1.html Graphics Classes | graphics.html Grouped Classes | groups.html Header File Index | headers.html @@ -126,7 +123,6 @@ Pictures of Most TQt Widgets | pictures.html Plugins | plugins.html Popup Widgets | popup-example.html Porting to TQt 3.x | porting.html -Preparing to Migrate the User Interface | motif-walkthrough-2.html Presenting the GUI | tutorial2-05.html Progress Bar | progressbar-example.html Progress Bar and Dialog Example | progress-example.html @@ -558,17 +554,10 @@ TQMimeSource Class | tqmimesource.html TQMimeSource Member List | tqmimesource-members.html TQMimeSourceFactory Class | tqmimesourcefactory.html TQMimeSourceFactory Member List | tqmimesourcefactory-members.html -TQMotif Class | tqmotif.html -TQMotif Member List | tqmotif-members.html -TQMotif Support Extension | motif-examples.html -TQMotifDialog Class | tqmotifdialog.html -TQMotifDialog Member List | tqmotifdialog-members.html TQMotifPlusStyle Class | tqmotifplusstyle.html TQMotifPlusStyle Member List | tqmotifplusstyle-members.html TQMotifStyle Class | tqmotifstyle.html TQMotifStyle Member List | tqmotifstyle-members.html -TQMotifWidget Class | tqmotifwidget.html -TQMotifWidget Member List | tqmotifwidget-members.html TQMouseEvent Class | tqmouseevent.html TQMouseEvent Member List | tqmouseevent-members.html TQMoveEvent Class | tqmoveevent.html @@ -926,16 +915,12 @@ TQXmlReader Class | tqxmlreader.html TQXmlReader Member List | tqxmlreader-members.html TQXmlSimpleReader Class | tqxmlsimplereader.html TQXmlSimpleReader Member List | tqxmlsimplereader-members.html -QXtWidget Class | qxtwidget.html -QXtWidget Member List | qxtwidget-members.html Qt Class | tqt.html Qt Commercial Editions | commercialeditions.html Qt Demo | demo-example.html Qt Distribution Example | distributor-example.html Qt Editions | editions.html Qt Member List | qt-members.html -Qt Motif Extension | motif-extension.html -Qt Motif Extension - A Migration Walkthrough | motif-walkthrough.html Qt Object Model | object.html Qt Open Source Edition | opensourceedition.html Qt Open Source Edition License Agreement | license.html @@ -967,9 +952,6 @@ Qt's Tools | tools-list.html Qt/Mac Issues | mac-differences.html Qt/Mac is Mac OS X Native | qtmac-as-native.html Range controls | rangecontrols-example.html -Refactoring Existing Code | motif-walkthrough-7.html -Replacing the Print Dialog | motif-walkthrough-9.html -Replacing the View Widget | motif-walkthrough-8.html Richtext | richtext-example.html Rot13 | rot-example.html SQL Module | sql.html @@ -1020,13 +1002,8 @@ Trademarks | trademarks.html Transformed Graphics Demo | xform-example.html Tutorial #2 | tutorial2.html User Interface Compiler (uic) | uic.html -Using Custom TQDialogs | motif-walkthrough-4.html -Using Existing Dialogs with TQMotifDialog | motif-walkthrough-5.html -Using TQt Main Window Classes | motif-walkthrough-6.html -Using TQt Standard Dialogs | motif-walkthrough-3.html Using menus | menu-example.html Using the Meta Object Compiler | moc.html -Using the Motif Event Loop | motif-customwidget-example.html Walkthrough: A Simple Application | simple-application.html Walkthrough: How to use the TQt SAX2 classes | xml-sax-walkthrough.html Walkthrough: Using SAX2 features with the TQt XML classes | xml-sax-features-walkthrough.html @@ -1163,11 +1140,8 @@ tqmenudata.h Include File | tqmenudata-h.html tqmessagebox.h Include File | tqmessagebox-h.html tqmetaobject.h Include File | tqmetaobject-h.html tqmime.h Include File | tqmime-h.html -tqmotif.h Include File | tqmotif-h.html -tqmotifdialog.h Include File | tqmotifdialog-h.html tqmotifplusstyle.h Include File | tqmotifplusstyle-h.html tqmotifstyle.h Include File | tqmotifstyle-h.html -tqmotifwidget.h Include File | tqmotifwidget-h.html tqmovie.h Include File | tqmovie-h.html tqmultilineedit.h Include File | tqmultilineedit-h.html tqmutex.h Include File | tqmutex-h.html @@ -1297,7 +1271,6 @@ tqwizard.h Include File | tqwizard-h.html tqwmatrix.h Include File | tqwmatrix-h.html tqworkspace.h Include File | tqworkspace-h.html tqxml.h Include File | tqxml-h.html -qxtwidget.h Include File | qxtwidget-h.html sql/overview/basicbrowsing/main.cpp Example File | sql-overview-basicbrowsing-main-cpp.html sql/overview/basicbrowsing2/main.cpp Example File | sql-overview-basicbrowsing2-main-cpp.html sql/overview/basicdatamanip/main.cpp Example File | sql-overview-basicdatamanip-main-cpp.html diff --git a/doc/html/tqcdestyle.html b/doc/html/tqcdestyle.html index 5db7db60..62d33dfc 100644 --- a/doc/html/tqcdestyle.html +++ b/doc/html/tqcdestyle.html @@ -46,7 +46,7 @@ body { background: #ffffff; color: black; } The TQCDEStyle class provides a CDE look and feel.

    -

    This style provides a slightly improved Motif look similar to some +

    This style provides a slightly improved Motif look similar to some versions of the Common Desktop Environment (CDE). The main differences are thinner frames and more modern radio buttons and checkboxes. Together with a dark background and a bright @@ -62,7 +62,7 @@ documentation. Constructs a TQCDEStyle.

    If useHighlightCols is FALSE (the default), then the style will -polish the application's color palette to emulate the Motif way of +polish the application's color palette to emulate the Motif way of highlighting, which is a simple inversion between the base and the text color. diff --git a/doc/html/tqcolorgroup.html b/doc/html/tqcolorgroup.html index 51fcb788..1a66aab4 100644 --- a/doc/html/tqcolorgroup.html +++ b/doc/html/tqcolorgroup.html @@ -137,7 +137,7 @@ effects: By default, the shadow color is TQt::black.

    All of these are normally derived from Background and used in ways that depend on that relationship. For example, buttons depend -on it to make the bevels look attractive, and Motif scroll bars +on it to make the bevels look attractive, and Motif scroll bars depend on Mid to be slightly different from Background.

    Selected (marked) items have two roles:

      diff --git a/doc/html/tqcombobox.html b/doc/html/tqcombobox.html index 2d5a3914..f44a2ffd 100644 --- a/doc/html/tqcombobox.html +++ b/doc/html/tqcombobox.html @@ -126,7 +126,7 @@ which case the user can enter arbitrary strings. out of a list of options in a way that takes up the minimum amount of screen space.

      TQComboBox supports three different display styles: Aqua/Motif 1.x, -Motif 2.0 and Windows. In Motif 1.x, a combobox was called +Motif 2.0 and Windows. In Motif 1.x, a combobox was called XmOptionMenu. In Motif 2.0, OSF introduced an improved combobox and named that XmComboBox. TQComboBox provides both.

      TQComboBox provides two different constructors. The simplest @@ -222,7 +222,7 @@ implementation-dependent.

      TQComboBox::TQComboBox ( TQWidget * parent = 0, const char * name = 0 )

      Constructs a combobox widget with parent parent called name. -

      This constructor creates a popup list if the program uses Motif +

      This constructor creates a popup list if the program uses Motif (or Aqua) look and feel; this is compatible with Motif 1.x and Aqua.

      Note: If you use this constructor to create your TQComboBox, then @@ -231,7 +231,7 @@ use the other constructor.

      TQComboBox::TQComboBox ( bool rw, TQWidget * parent = 0, const char * name = 0 )

      -Constructs a combobox with a maximum size and either Motif 2.0 or +Constructs a combobox with a maximum size and either Motif 2.0 or Windows look and feel.

      The input field can be edited if rw is TRUE, otherwise the user may only choose one of the items in the combobox. @@ -565,7 +565,7 @@ setting.

      bool editable

      This property holds whether the combobox is editable.

      This property's default is FALSE. Note that the combobox will be -cleared if this property is set to TRUE for a 1.x Motif style +cleared if this property is set to TRUE for a 1.x Motif style combobox. To avoid this, use setEditable() before inserting any items. Also note that the 1.x version of Motif didn't have any editable comboboxes, so the combobox will change it's appearance @@ -583,7 +583,7 @@ to a 2.0 style Motif combobox is it is set to be editable.

      Set this property's value with setMaxCount() and get this property's value with maxCount().

      int sizeLimit

      This property holds the maximum on-screen size of the combobox. -

      This property is ignored for both Motif 1.x style and non-editable +

      This property is ignored for both Motif 1.x style and non-editable comboboxes in Mac style. The default limit is ten lines. If the number of items in the combobox is or grows larger than lines, a scrollbar is added. diff --git a/doc/html/tqdialog.html b/doc/html/tqdialog.html index 81cdca74..8fd4b2a5 100644 --- a/doc/html/tqdialog.html +++ b/doc/html/tqdialog.html @@ -35,7 +35,7 @@ body { background: #ffffff; color: black; } More...

      #include <tqdialog.h>

      Inherits TQWidget. -

      Inherited by TQColorDialog, TQErrorMessage, TQFileDialog, TQFontDialog, TQInputDialog, TQMessageBox, TQMotifDialog, TQProgressDialog, TQTabDialog, and TQWizard. +

      Inherited by TQColorDialog, TQErrorMessage, TQFileDialog, TQFontDialog, TQInputDialog, TQMessageBox, TQProgressDialog, TQTabDialog, and TQWizard.

      List of all member functions.

      Public Members

        @@ -252,7 +252,7 @@ blocking until the user closes it. The function returns a show() and result(). -

        Examples: chart/chartform.cpp, dialog/mainwindow.cpp, i18n/main.cpp, network/ftpclient/ftpmainwindow.ui.h, network/networkprotocol/view.cpp, tqdir/tqdir.cpp, and wizard/main.cpp. +

        Examples: chart/chartform.cpp, i18n/main.cpp, network/ftpclient/ftpmainwindow.ui.h, network/networkprotocol/view.cpp, tqdir/tqdir.cpp, and wizard/main.cpp.

        TQWidget * TQDialog::extension () const

        Returns the dialog's extension or 0 if no extension has been diff --git a/doc/html/tqeventloop.html b/doc/html/tqeventloop.html index fa71020d..8f9b4a44 100644 --- a/doc/html/tqeventloop.html +++ b/doc/html/tqeventloop.html @@ -35,7 +35,6 @@ body { background: #ffffff; color: black; } More...

        #include <tqeventloop.h>

        Inherits TQObject. -

        Inherited by TQMotif.

        List of all member functions.

        Public Members

        Both active and inactive windows can contain disabled widgets. (Disabled widgets are often called inaccessible or grayed out.) -

        In Motif style, active() and inactive() look the same. In Windows +

        In Motif style, active() and inactive() look the same. In Windows 2000 style and Macintosh Platinum style, the two styles look slightly different.

        There are setActive(), setInactive(), and setDisabled() functions diff --git a/doc/html/tqpopupmenu.html b/doc/html/tqpopupmenu.html index 153d718a..5f0fed3b 100644 --- a/doc/html/tqpopupmenu.html +++ b/doc/html/tqpopupmenu.html @@ -617,7 +617,7 @@ Inserts a separator at position index, and returns the Motif menu bar a separator is spacing, so the rest of the items +Motif menu bar a separator is spacing, so the rest of the items (normally just "Help") are drawn right-justified. In a Windows menu bar separators are ignored (to comply with the Windows style guidelines). diff --git a/doc/html/tqscrollbar.html b/doc/html/tqscrollbar.html index fdb214fb..4723ae61 100644 --- a/doc/html/tqscrollbar.html +++ b/doc/html/tqscrollbar.html @@ -122,7 +122,7 @@ values of pageStep() and lineStepminValue() and maxValue() of the scroll bar. TQScrollBar has a convenience constructor with which you can set most of these properties. -

        Some GUI styles (for example, the Windows and Motif styles +

        Some GUI styles (for example, the Windows and Motif styles provided with TQt), also use the pageStep() value to calculate the size of the slider.

        In addition to the access functions from TQRangeControl, TQScrollBar @@ -261,7 +261,7 @@ See the "pageStep" property for det

        void TQScrollBar::setPalette ( const TQPalette & p ) [virtual]

        Reimplements the virtual function TQWidget::setPalette(). -

        Sets the background color to the mid color for Motif style scroll +

        Sets the background color to the mid color for Motif style scroll bars using palette p.

        Reimplemented from TQWidget. diff --git a/doc/html/tqsgistyle.html b/doc/html/tqsgistyle.html index ca88af11..df958eae 100644 --- a/doc/html/tqsgistyle.html +++ b/doc/html/tqsgistyle.html @@ -47,7 +47,7 @@ body { background: #ffffff; color: black; } The TQSGIStyle class provides SGI/Irix look and feel.

        This class implements the SGI look and feel. It resembles the -SGI/Irix Motif GUI style as closely as TQStyle allows. +SGI/Irix Motif GUI style as closely as TQStyle allows.

        See also Widget Appearance and Style.


        Member Function Documentation

        @@ -55,7 +55,7 @@ SGI/Irix Motif GUI style as closely as Constructs a TQSGIStyle.

        If useHighlightCols is FALSE (default value), the style will -polish the application's color palette to emulate the Motif way of +polish the application's color palette to emulate the Motif way of highlighting, which is a simple inversion between the base and the text color.

        See also TQMotifStyle::useHighlightColors(). diff --git a/doc/html/tqslider.html b/doc/html/tqslider.html index 10f18788..8071d338 100644 --- a/doc/html/tqslider.html +++ b/doc/html/tqslider.html @@ -206,7 +206,7 @@ See the "pageStep" property for detail

        void TQSlider::setPalette ( const TQPalette & p ) [virtual]

        Reimplements the virtual function TQWidget::setPalette(). -

        Sets the background color to the mid color for Motif style sliders +

        Sets the background color to the mid color for Motif style sliders using palette p.

        Reimplemented from TQWidget. diff --git a/doc/html/tqstyle.html b/doc/html/tqstyle.html index 0bc44a39..5d750358 100644 --- a/doc/html/tqstyle.html +++ b/doc/html/tqstyle.html @@ -88,7 +88,7 @@ The TQStyle class specifies the look and feel of a GUI.

        A large number of GUI elements are common to many widgets. The TQStyle class allows the look of these elements to be modified across all widgets that use the TQStyle functions. It also -provides two feel options: Motif and Windows. +provides two feel options: Motif and Windows.

        Although it is not possible to fully enumerate the look of graphical elements and the feel of widgets in a GUI, TQStyle provides a considerable amount of control and customisability. @@ -446,7 +446,7 @@ like Windows

      • TQStyle::SH_Slider_SloppyKeyEvents - key presses handled in a sloppy manner, i.e. left on a vertical slider subtracts a line.
      • TQStyle::SH_ProgressDialog_CenterCancelButton - center button on -progress dialogs, like Motif, otherwise right aligned. +progress dialogs, like Motif, otherwise right aligned.
      • TQStyle::SH_ProgressDialog_TextLabelAlignment - TQt::AlignmentFlags -- text label alignment in progress dialogs; Center on windows, Auto|VCenter otherwise. diff --git a/doc/html/tqwidget.html b/doc/html/tqwidget.html index 2cf57943..00f5f0fc 100644 --- a/doc/html/tqwidget.html +++ b/doc/html/tqwidget.html @@ -35,7 +35,7 @@ body { background: #ffffff; color: black; } More...

        #include <tqwidget.h>

        Inherits TQObject and TQPaintDevice. --

        Inherited by TQButton, TQFrame, TQDialog, TQComboBox, TQDataBrowser, TQDataView, TQDateTimeEditBase, TQDateTimeEdit, TQDesktopWidget, TQDial, TQDockArea, TQGLWidget, TQHeader, TQMainWindow, TQMotifWidget, TQScrollBar, TQSizeGrip, TQSlider, TQSpinBox, TQSplashScreen, TQStatusBar, TQTabBar, TQTabWidget, TQWorkspace, and TQXtWidget. +-

        Inherited by TQButton, TQFrame, TQDialog, TQComboBox, TQDataBrowser, TQDataView, TQDateTimeEditBase, TQDateTimeEdit, TQDesktopWidget, TQDial, TQDockArea, TQGLWidget, TQHeader, TQMainWindow, TQScrollBar, TQSizeGrip, TQSlider, TQSpinBox, TQSplashScreen, TQStatusBar, TQTabBar, TQTabWidget and TQWorkspace.

        List of all member functions.

        Public Members

          @@ -840,7 +840,7 @@ otherwise returns FALSE.

          The TQApplication::lastWindowClosed() signal is emitted when the last visible top level widget is closed.

          -

          Examples: dialog/mainwindow.cpp, mdi/application.cpp, popup/popup.cpp, and toplevel/options.ui.h. +

          Examples: mdi/application.cpp, popup/popup.cpp, and toplevel/options.ui.h.

          bool TQWidget::close ( bool alsoDelete ) [virtual]

          This is an overloaded member function, provided for convenience. It behaves essentially like the above function. @@ -1866,9 +1866,8 @@ the window has done something. This is because Microsoft do not allow an application to interrupt what the user is currently doing in another application.

          See also isActiveWindow, topLevelWidget(), and show(). - -

          Reimplemented in TQXtWidget.

          void TQWidget::setAutoMask ( bool ) [virtual] +

          Sets whether the auto mask feature is enabled for the widget. See the "autoMask" property for details.

          void TQWidget::setBackgroundColor ( const TQColor & c ) [virtual] @@ -2538,7 +2537,6 @@ a TQt event and sends it to the widget.

          Warning: This function is not portable.

          See also TQApplication::x11EventFilter(). -

          Reimplemented in TQXtWidget.

          int TQWidget::y () const

          Returns the y coordinate of the widget relative to its parent and including any window frame. See the "y" property for details. diff --git a/doc/html/whatsthis b/doc/html/whatsthis index 6ffd4e04..433b49c0 100644 --- a/doc/html/whatsthis +++ b/doc/html/whatsthis @@ -332,8 +332,6 @@ Template class which ensures that implicitly shared and explicitly shared classe Template collection class that provides a vector (array). | TQPtrVector Text object on a TQCanvas. | TQCanvasText Text or image display. | TQLabel -The TQDialog API for Motif-based dialogs. | TQMotifDialog -The TQWidget API for Xt/Motif widgets. | TQMotifWidget The XML handler classes with information about the parsing position within a file. | TQXmlLocator The abstract base class of button widgets, providing functionality common to buttons. | TQButton The base class for all the nodes in a DOM tree. | TQDomNode @@ -347,7 +345,6 @@ The base class of geometry managers. | TQLayout The base class of most pointer-based TQt collections. | TQPtrCollection The base class of objects that can be painted. | TQPaintDevice The base class of widgets that can have a frame. | TQFrame -The basis of the Motif Extension. | TQMotif The cell content for TQTable cells. | TQTableItem The display format of an OpenGL rendering context. | TQGLFormat The input data for the TQXmlReader subclasses. | TQXmlInputSource diff --git a/doc/indices.doc b/doc/indices.doc index 88f60d3c..084c60c5 100644 --- a/doc/indices.doc +++ b/doc/indices.doc @@ -150,7 +150,6 @@ Licenses & Credits \list \i \link winsystem.html Window system specific notes\endlink -\i \link motif-extension.html Motif Extension\endlink \i \link mac-differences.html Mac OS X development\endlink \i \link porting.html Porting from TQt 2.x to TQt 3.x\endlink \endlist @@ -355,15 +354,6 @@ in a line-by-line coverage please refer to the tutorials \i \link sql-examples.html SQL examples \endlink \endlist -\section1 TQt Extensions: Assorted Examples - -\list -\i \link motif-examples.html TQMotif support extension \endlink -\omit \i \link xt-motif-examples.html Xt/Motif support extension \endlink \endomit -\endlist - -\section1 Miscellaneous Examples - */ /*! \defgroup tqaction-examples @@ -438,31 +428,6 @@ Qt XML classes. */ -/*! \defgroup motif-examples - -\title TQMotif Support Extension - -The following example programs illustrate the use of the TQMotif Extension -assisting in the migration process of old Xt and Motif based code -to the more comfortable TQt toolkit. - -For more information see the \link motif-extension.html TQMotif -Support Extension documentation. \endlink -*/ - -/* -\defgroup xt-motif-examples - -\title TQt Xt/Motif Support Extension - -The following example programs illustrate the use of the TQt Xt/Motif Extension -assisting in the migration process of old Xt and Motif based code -to the more comfortable TQt toolkit. - -For more information see the \link xt.html TQt Xt/Motif Support -Extension documentation. \endlink -*/ - /*! \defgroup step-by-step-examples \title Step-by-step Examples diff --git a/doc/man/man3/TQMotif.3qt b/doc/man/man3/TQMotif.3qt deleted file mode 100644 index 65b5244e..00000000 --- a/doc/man/man3/TQMotif.3qt +++ /dev/null @@ -1 +0,0 @@ -.so man3/tqmotif.3qt diff --git a/doc/man/man3/TQMotifDialog.3qt b/doc/man/man3/TQMotifDialog.3qt deleted file mode 100644 index b0c0e8e8..00000000 --- a/doc/man/man3/TQMotifDialog.3qt +++ /dev/null @@ -1 +0,0 @@ -.so man3/tqmotifdialog.3qt diff --git a/doc/man/man3/TQMotifWidget.3qt b/doc/man/man3/TQMotifWidget.3qt deleted file mode 100644 index bcb90c72..00000000 --- a/doc/man/man3/TQMotifWidget.3qt +++ /dev/null @@ -1 +0,0 @@ -.so man3/tqmotifwidget.3qt diff --git a/doc/man/man3/tqdialog.3qt b/doc/man/man3/tqdialog.3qt index 37463429..80cc1b7f 100644 --- a/doc/man/man3/tqdialog.3qt +++ b/doc/man/man3/tqdialog.3qt @@ -13,7 +13,7 @@ TQDialog \- The base class of dialog windows .PP Inherits TQWidget. .PP -Inherited by TQColorDialog, TQErrorMessage, TQFileDialog, TQFontDialog, TQInputDialog, TQMessageBox, TQMotifDialog, TQProgressDialog, TQTabDialog, and TQWizard. +Inherited by TQColorDialog, TQErrorMessage, TQFileDialog, TQFontDialog, TQInputDialog, TQMessageBox, TQProgressDialog, TQTabDialog, and TQWizard. .PP .SS "Public Members" .in +1c diff --git a/doc/man/man3/tqeventloop.3qt b/doc/man/man3/tqeventloop.3qt index c7308621..55c907fe 100644 --- a/doc/man/man3/tqeventloop.3qt +++ b/doc/man/man3/tqeventloop.3qt @@ -13,8 +13,6 @@ TQEventLoop \- Manages the event queue .PP Inherits TQObject. .PP -Inherited by TQMotif. -.PP .SS "Public Members" .in +1c .ti -1c @@ -91,7 +89,7 @@ It receives events from the window system and other sources. It then sends them .PP TQEventLoop allows the application programmer to have more control over event delivery. Programs that perform long operations can call either processOneEvent() or processEvents() with various ProcessEvent values OR'ed together to control which events should be delivered. .PP -TQEventLoop also allows the integration of an external event loop with the TQt event loop. The Motif Extension included with TQt includes a reimplementation of TQEventLoop for merging TQt and Motif events together. +TQEventLoop also allows the integration of an external event loop with the TQt event loop. .PP To use your own instance of TQEventLoop or TQEventLoop subclass create it before you create the QApplication object. .PP diff --git a/doc/man/man3/tqmotif.3qt b/doc/man/man3/tqmotif.3qt deleted file mode 100644 index 670531e1..00000000 --- a/doc/man/man3/tqmotif.3qt +++ /dev/null @@ -1,114 +0,0 @@ -'\" t -.TH TQMotif 3qt "2 February 2007" "Trolltech AS" \" -*- nroff -*- -.\" Copyright 1992-2007 Trolltech ASA. All rights reserved. See the -.\" license file included in the distribution for a complete license -.\" statement. -.\" -.ad l -.nh -.SH NAME -TQMotif \- The basis of the -.SH SYNOPSIS -This class is part of the \fBQt Motif Extension\fR. -.PP -\fC#include \fR -.PP -Inherits TQEventLoop. -.PP -.SS "Public Members" -.in +1c -.ti -1c -.BI "\fBTQMotif\fR ( const char * applicationClass, XtAppContext context = NULL, XrmOptionDescRec * options = 0, int numOptions = 0 )" -.br -.ti -1c -.BI "\fB~TQMotif\fR ()" -.br -.ti -1c -.BI "XtAppContext \fBapplicationContext\fR () const" -.br -.in -1c -.SS "Static Public Members" -.in +1c -.ti -1c -.BI "Display * \fBx11Display\fR ()" -.br -.in -1c -.SH DESCRIPTION -This class is defined in the \fBQt Motif Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main TQt API. -.PP -The TQMotif class provides the basis of the Motif Extension. -.PP -TQMotif only provides a few public functions, but it is at the heart of the integration. TQMotif is responsible for initializing the Xt toolkit and the Xt application context. It does not open a connection to the X server, that is done by QApplication. -.PP -The only member function in TQMotif that depends on an X server connection is TQMotif::initialize(). TQMotif must be created before QApplication. -.PP -Example usage of TQMotif and QApplication: -.PP -.nf -.br - static char *resources[] = { -.br - ... -.br - }; -.br -.br - int main(int argc, char **argv) -.br - { -.br - TQMotif integrator( "AppClass" ); -.br - XtAppSetFallbackResources( integrator.applicationContext(), -.br - resources ); -.br - QApplication app( argc, argv ); -.br -.br - ... -.br -.br - return app.exec(); -.br - } -.br -.fi -.SH MEMBER FUNCTION DOCUMENTATION -.SH "TQMotif::TQMotif ( const char * applicationClass, XtAppContext context = NULL, XrmOptionDescRec * options = 0, int numOptions = 0 )" -Creates TQMotif, which allows TQt and Xt/Motif integration. -.PP -If \fIcontext\fR is 0, TQMotif creates a default application context itself. The context is accessible through applicationContext(). -.PP -All arguments passed to this function (\fIapplicationClass\fR, \fIoptions\fR and \fInumOptions\fR) are used to call XtDisplayInitialize() after QApplication has been constructed. -.SH "TQMotif::~TQMotif ()" -Destroys TQMotif. -.SH "XtAppContext TQMotif::applicationContext () const" -Returns the application context. -.SH "Display * TQMotif::x11Display ()\fC [static]\fR" -Returns the X11 display connection used by the TQt Motif Extension. - -.SH "SEE ALSO" -.BR http://doc.trolltech.com/tqmotif.html -.BR http://www.trolltech.com/faq/tech.html -.SH COPYRIGHT -Copyright 1992-2007 Trolltech ASA, http://www.trolltech.com. See the -license file included in the distribution for a complete license -statement. -.SH AUTHOR -Generated automatically from the source code. -.SH BUGS -If you find a bug in Qt, please report it as described in -.BR http://doc.trolltech.com/bughowto.html . -Good bug reports help us to help you. Thank you. -.P -The definitive TQt documentation is provided in HTML format; it is -located at $TQTDIR/doc/html and can be read using TQt Assistant or with -a web browser. This man page is provided as a convenience for those -users who prefer man pages, although this format is not officially -supported by Trolltech. -.P -If you find errors in this manual page, please report them to -.BR qt-bugs@trolltech.com . -Please include the name of the manual page (tqmotif.3qt) and the Qt -version (3.3.8). diff --git a/doc/man/man3/tqmotifdialog.3qt b/doc/man/man3/tqmotifdialog.3qt deleted file mode 100644 index 6589a3c8..00000000 --- a/doc/man/man3/tqmotifdialog.3qt +++ /dev/null @@ -1,178 +0,0 @@ -'\" t -.TH TQMotifDialog 3qt "2 February 2007" "Trolltech AS" \" -*- nroff -*- -.\" Copyright 1992-2007 Trolltech ASA. All rights reserved. See the -.\" license file included in the distribution for a complete license -.\" statement. -.\" -.ad l -.nh -.SH NAME -TQMotifDialog \- The TQDialog API for Motif-based dialogs -.SH SYNOPSIS -This class is part of the \fBQt Motif Extension\fR. -.PP -\fC#include \fR -.PP -Inherits TQDialog. -.PP -.SS "Public Members" -.in +1c -.ti -1c -.BI "enum DialogType { Prompt, Selection, Command, FileSelection, Template, Error, Information, Message, Question, Warning, Working } \fI(obsolete)\fR" -.br -.ti -1c -.BI "TQMotifDialog ( DialogType dialogtype, Widget parent, ArgList args = NULL, Cardinal argcount = 0, const char * name = 0, bool modal = FALSE, WFlags flags = 0 ) \fI(obsolete)\fR" -.br -.ti -1c -.BI "TQMotifDialog ( Widget parent, ArgList args = NULL, Cardinal argcount = 0, const char * name = 0, bool modal = FALSE, WFlags flags = 0 ) \fI(obsolete)\fR" -.br -.ti -1c -.BI "\fBTQMotifDialog\fR ( Widget parent, const char * name = 0, bool modal = FALSE, WFlags flags = 0 )" -.br -.ti -1c -.BI "\fBTQMotifDialog\fR ( TQWidget * parent, const char * name = 0, bool modal = FALSE, WFlags flags = 0 )" -.br -.ti -1c -.BI "virtual \fB~TQMotifDialog\fR ()" -.br -.ti -1c -.BI "Widget \fBshell\fR () const" -.br -.ti -1c -.BI "Widget \fBdialog\fR () const" -.br -.in -1c -.SS "Static Public Members" -.in +1c -.ti -1c -.BI "void \fBacceptCallback\fR ( Widget, XtPointer client_data, XtPointer )" -.br -.ti -1c -.BI "void \fBrejectCallback\fR ( Widget, XtPointer client_data, XtPointer )" -.br -.in -1c -.SH DESCRIPTION -This class is defined in the \fBQt Motif Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main TQt API. -.PP -The TQMotifDialog class provides the TQDialog API for Motif-based dialogs. -.PP -TQMotifDialog provides two separate modes of operation. The application programmer can use TQMotifDialog with an existing Motif-based dialog and a TQWidget parent, or the application programmer can use TQMotifDialog with a custom Qt-based dialog and a Motif-based parent. Modality continues to work as expected. -.PP -Motif-based dialogs must have a \fCShell\fR widget parent with a single child, due to requirements of the Motif toolkit. The \fCShell\fR widget, which is a special subclass of \fCXmDialogShell\fR, is created during construction. It can be accessed using the shell() member function. -.PP -The single child of the \fCShell\fR can be accessed using the dialog() member function \fIafter\fR it has been created. -.PP -The acceptCallback() and rejectCallback() functions provide a convenient way to call TQDialog::accept() and TQDialog::reject() through callbacks. A pointer to the TQMotifDialog should be passed as the \fCclient_data\fR argument to the callback. -.PP -The API and behavior TQMotifDialog is identical to that of TQDialog when using a custom Qt-based dialog with a Motif-based parent. The only difference is that a Motif-based \fIparent\fR argument is passed to the constructor, instead of a TQWidget parent. -.SS "Member Type Documentation" -.SH "TQMotifDialog::DialogType" -\fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code. -.PP -This enum lists the predefined Motif dialog types. -.TP -\fCTQMotifDialog::Prompt\fR -.TP -\fCTQMotifDialog::Selection\fR -.TP -\fCTQMotifDialog::Command\fR -.TP -\fCTQMotifDialog::FileSelection\fR -.TP -\fCTQMotifDialog::Template\fR -.TP -\fCTQMotifDialog::Error\fR -.TP -\fCTQMotifDialog::Information\fR -.TP -\fCTQMotifDialog::Message\fR -.TP -\fCTQMotifDialog::Question\fR -.TP -\fCTQMotifDialog::Warning\fR -.TP -\fCTQMotifDialog::Working\fR -.SH MEMBER FUNCTION DOCUMENTATION -.SH "TQMotifDialog::TQMotifDialog ( DialogType dialogtype, Widget parent, ArgList args = NULL, Cardinal argcount = 0, const char * name = 0, bool modal = FALSE, WFlags flags = 0 )" -\fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code. -.PP -Creates a TQMotifDialog using one of the predefined Motif dialog types. The \fIname\fR, \fImodal\fR and \fIflags\fR arguments are passed to the TQDialog constructor. -.PP -This constructor creates a Shell widget, which is a special subclass of XmDialogShell. The \fIparent\fR, \fIargs\fR and \fIargcount\fR arguments are passed to XtCreatePopupShell() when creating the subclass. You can access the Shell widget with the shell() member function. -.PP -This constructor also creates the dialog widget with the Shell widget as its parent. The type of the dialog created is specified by the \fIdialogtype\fR argument. See the DialogType enum for a list of available dialog types. You can access the dialog widget with the dialog() member function. -.PP -\fBWarning:\fR TQMotifDialog takes ownership of the child widget and destroys it during destruction. You should not destroy the dialog widget yourself. -.PP -See also DialogType, shell(), and dialog(). -.SH "TQMotifDialog::TQMotifDialog ( Widget parent, ArgList args = NULL, Cardinal argcount = 0, const char * name = 0, bool modal = FALSE, WFlags flags = 0 )" -\fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code. -.PP -Creates a TQMotifDialog which allows the application programmer to use the Motif-based \fIparent\fR for a custom TQDialog. The \fIname\fR, \fImodal\fR and \fIflags\fR arguments are passed to the TQDialog constructor. -.PP -This constructor creates a Shell widget, which is a special subclass of XmDialogShell. The \fIargs\fR and \fIargcount\fR arguments are passed to XtCreatePopupShell() when creating the subclass. You can access the Shell widget with the shell() member function. -.PP -The dialog widget is not created by the constructor. You must create the dialog widget as a child of the the widget returned by shell(). You can access the child widget with the dialog() member function. -.PP -A dialog widget is not created by this constructor. Instead, you should create the dialog widget as a child of this dialog. TQMotifDialog will take ownership of your custom dialog, and you can access it with the dialog() member function. -.PP -\fBWarning:\fR TQMotifDialog takes ownership of the child widget and destroys it during destruction. You should not destroy the dialog widget yourself. -.PP -See also shell() and dialog(). -.SH "TQMotifDialog::TQMotifDialog ( Widget parent, const char * name = 0, bool modal = FALSE, WFlags flags = 0 )" -Creates a TQMotifDialog which allows the application programmer to use the Motif-based \fIparent\fR for a custom TQDialog. The \fIname\fR, \fImodal\fR and \fIflags\fR arguments are passed to the TQDialog constructor. -.PP -This constructor creates a \fCShell\fR widget, which is a special subclass of \fCXmDialogShell\fR. You can access the \fCShell\fR widget with the shell() member function. -.PP -See also shell(). -.SH "TQMotifDialog::TQMotifDialog ( TQWidget * parent, const char * name = 0, bool modal = FALSE, WFlags flags = 0 )" -Creates a TQMotifDialog which allows the application programmer to use a TQWidget parent for an existing Motif-based dialog. The \fIparent\fR, \fIname\fR, \fImodal\fR and \fIflags\fR arguments are passed to the TQDialog constructor. -.PP -This constructor creates a \fCShell\fR widget, which is a special subclass of \fCXmDialogShell\fR. You can access the \fCShell\fR widget with the shell() member functon. -.PP -A dialog widget is not created by this constructor. Instead, you should create the dialog widget as a child of this dialog. TQMotifDialog will take ownership of your custom dialog, and you can access it with the dialog() member function. -.PP -\fBWarning:\fR TQMotifDialog takes ownership of the child widget and destroys it during destruction. You should not destroy the dialog widget yourself. -.PP -See also shell() and dialog(). -.SH "TQMotifDialog::~TQMotifDialog ()\fC [virtual]\fR" -Destroys the TQDialog, dialog widget and \fCShell\fR widget. -.SH "void TQMotifDialog::acceptCallback ( Widget, XtPointer client_data, XtPointer )\fC [static]\fR" -Convenient Xt/Motif callback to accept the TQMotifDialog. -.PP -The data is passed in \fIclient_data\fR. -.SH "Widget TQMotifDialog::dialog () const" -Returns the Motif widget embedded in this dialog. -.SH "void TQMotifDialog::rejectCallback ( Widget, XtPointer client_data, XtPointer )\fC [static]\fR" -Convenient Xt/Motif callback to reject the TQMotifDialog. -.PP -The data is passed in \fIclient_data\fR. -.SH "Widget TQMotifDialog::shell () const" -Returns the \fCShell\fR widget embedded in this dialog. -.PP -Example: dialog/mainwindow.cpp. - -.SH "SEE ALSO" -.BR http://doc.trolltech.com/tqmotifdialog.html -.BR http://www.trolltech.com/faq/tech.html -.SH COPYRIGHT -Copyright 1992-2007 Trolltech ASA, http://www.trolltech.com. See the -license file included in the distribution for a complete license -statement. -.SH AUTHOR -Generated automatically from the source code. -.SH BUGS -If you find a bug in Qt, please report it as described in -.BR http://doc.trolltech.com/bughowto.html . -Good bug reports help us to help you. Thank you. -.P -The definitive TQt documentation is provided in HTML format; it is -located at $TQTDIR/doc/html and can be read using TQt Assistant or with -a web browser. This man page is provided as a convenience for those -users who prefer man pages, although this format is not officially -supported by Trolltech. -.P -If you find errors in this manual page, please report them to -.BR qt-bugs@trolltech.com . -Please include the name of the manual page (tqmotifdialog.3qt) and the Qt -version (3.3.8). diff --git a/doc/man/man3/tqmotifwidget.3qt b/doc/man/man3/tqmotifwidget.3qt deleted file mode 100644 index 3b12c0a4..00000000 --- a/doc/man/man3/tqmotifwidget.3qt +++ /dev/null @@ -1,86 +0,0 @@ -'\" t -.TH TQMotifWidget 3qt "2 February 2007" "Trolltech AS" \" -*- nroff -*- -.\" Copyright 1992-2007 Trolltech ASA. All rights reserved. See the -.\" license file included in the distribution for a complete license -.\" statement. -.\" -.ad l -.nh -.SH NAME -TQMotifWidget \- The TQWidget API for Xt/Motif widgets -.SH SYNOPSIS -This class is part of the \fBQt Motif Extension\fR. -.PP -\fC#include \fR -.PP -Inherits TQWidget. -.PP -.SS "Public Members" -.in +1c -.ti -1c -.BI "\fBTQMotifWidget\fR ( TQWidget * parent, WidgetClass widgetclass, ArgList args = NULL, Cardinal argcount = 0, const char * name = 0, WFlags flags = 0 )" -.br -.ti -1c -.BI "virtual \fB~TQMotifWidget\fR ()" -.br -.ti -1c -.BI "Widget \fBmotifWidget\fR () const" -.br -.in -1c -.SS "Protected Members" -.in +1c -.ti -1c -.BI "virtual bool \fBx11Event\fR ( XEvent * event )" -.br -.in -1c -.SH DESCRIPTION -This class is defined in the \fBQt Motif Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main TQt API. -.PP -The TQMotifWidget class provides the TQWidget API for Xt/Motif widgets. -.PP -TQMotifWidget exists to provide a TQWidget that can act as a parent for any Xt/Motif widget. Since the TQMotifWidget is a proper TQWidget, it can be used as a top-level widget (e.g. 0 parent) or as a child of any other TQWidget. Note: Since TQMotifWidget acts as a parent for Xt/Motif widgets, you should not create TQWidgets with a TQMotifWidget parent. -.PP -An Xt/Motif widget with a top-level TQMotifWidget parent can begin using the standard TQt dialogs and custom TQDialogs while keeping the main Xt/Motif interface of the application. Using a TQMotifWidget as the parent for the various TQDialogs will ensure that modality and stacking works properly throughout the entire application. -.PP -Applications moving to TQt may have custom Xt/Motif widgets that will take time to rewrite with Qt. Such applications can use these custom widgets as TQMotifWidget with TQWidget parents. This allows the application's interface to be replaced gradually. -.PP -\fBWarning:\fR TQMotifWidget uses the X11 window ID of the Motif widget directly, instead of creating its own. Because ot this, TQWidget::reparent() will not work. This includes the functions TQWidget::showFullScreen() and TQWidget::showNormal(), which use TQWidget::reparent(). -.SH MEMBER FUNCTION DOCUMENTATION -.SH "TQMotifWidget::TQMotifWidget ( TQWidget * parent, WidgetClass widgetclass, ArgList args = NULL, Cardinal argcount = 0, const char * name = 0, WFlags flags = 0 )" -Creates a TQMotifWidget of the given \fIwidgetclass\fR as a child of \fIparent\fR, with the name \fIname\fR and widget flags \fIflags\fR. -.PP -The \fIargs\fR and \fIargcount\fR arguments are passed on to XtCreateWidget. -.PP -The motifWidget() function returns the resulting Xt/Motif widget. This widget can be used as a parent for any other Xt/Motif widget. -.PP -If \fIparent\fR is a TQMotifWidget, the Xt/Motif widget is created as a child of the parent's motifWidget(). If \ parent is 0 or a normal TQWidget, the Xt/Motif widget is created as a child of a special TopLevelShell widget. Xt/Motif widgets can use this special TopLevelShell parent as the parent for existing Xt/Motif dialogs or TQMotifDialogs. -.SH "TQMotifWidget::~TQMotifWidget ()\fC [virtual]\fR" -Destroys the TQMotifWidget. The special TopLevelShell is also destroyed, if it was created during construction. -.SH "Widget TQMotifWidget::motifWidget () const" -Returns the embedded Xt/Motif widget. If a Shell widget was -created by the constructor, you can access it with XtParent(). - -.SH "SEE ALSO" -.BR http://doc.trolltech.com/tqmotifwidget.html -.BR http://www.trolltech.com/faq/tech.html -.SH COPYRIGHT -Copyright 1992-2007 Trolltech ASA, http://www.trolltech.com. See the -license file included in the distribution for a complete license -statement. -.SH AUTHOR -Generated automatically from the source code. -.SH BUGS -If you find a bug in Qt, please report it as described in -.BR http://doc.trolltech.com/bughowto.html . -Good bug reports help us to help you. Thank you. -.P -The definitive TQt documentation is provided in HTML format; it is -located at $TQTDIR/doc/html and can be read using TQt Assistant or with -a web browser. This man page is provided as a convenience for those -users who prefer man pages, although this format is not officially -supported by Trolltech. -.P -If you find errors in this manual page, please report them to -.BR qt-bugs@trolltech.com . -Please include the name of the manual page (tqmotifwidget.3qt) and the Qt -version (3.3.8). diff --git a/doc/man/man3/tqwidget.3qt b/doc/man/man3/tqwidget.3qt index b8f31822..d95f88ee 100644 --- a/doc/man/man3/tqwidget.3qt +++ b/doc/man/man3/tqwidget.3qt @@ -13,7 +13,7 @@ TQWidget \- The base class of all user interface objects .PP Inherits TQObject and TQPaintDevice. .PP -Inherited by TQButton, TQFrame, TQDialog, TQComboBox, TQDataBrowser, TQDataView, TQDateTimeEditBase, TQDateTimeEdit, TQDesktopWidget, TQDial, TQDockArea, TQGLWidget, TQHeader, TQMainWindow, TQMotifWidget, TQScrollBar, TQSizeGrip, TQSlider, TQSpinBox, TQSplashScreen, TQStatusBar, TQTabBar, TQTabWidget, TQWorkspace, and QXtWidget. +Inherited by TQButton, TQFrame, TQDialog, TQComboBox, TQDataBrowser, TQDataView, TQDateTimeEditBase, TQDateTimeEdit, TQDesktopWidget, TQDial, TQDockArea, TQGLWidget, TQHeader, TQMainWindow, TQScrollBar, TQSizeGrip, TQSlider, TQSpinBox, TQSplashScreen, TQStatusBar, TQTabBar, TQTabWidget and TQWorkspace. .PP .SS "Public Members" .in +1c @@ -1978,8 +1978,6 @@ This function performs the same operation as clicking the mouse on the title bar On Windows, if you are calling this when the application is not currently the active one then it will not make it the active window. It will flash the task bar entry blue to indicate that the window has done something. This is because Microsoft do not allow an application to interrupt what the user is currently doing in another application. .PP See also isActiveWindow, topLevelWidget(), and show(). -.PP -Reimplemented in QXtWidget. .SH "void TQWidget::setAutoMask ( bool )\fC [virtual]\fR" Sets whether the auto mask feature is enabled for the widget. See the "autoMask" property for details. .SH "void TQWidget::setBackgroundColor ( const TQColor & c )\fC [virtual]\fR" @@ -2508,8 +2506,6 @@ In your reimplementation of this function, if you want to stop the event being h \fBWarning:\fR This function is not portable. .PP See also QApplication::x11EventFilter(). -.PP -Reimplemented in QXtWidget. .SH "int TQWidget::y () const" Returns the y coordinate of the widget relative to its parent and including any window frame. See the "y" property for details. .SS "Property Documentation" diff --git a/doc/modules.doc b/doc/modules.doc index 9f4bc55a..82c14052 100644 --- a/doc/modules.doc +++ b/doc/modules.doc @@ -60,7 +60,6 @@ with each Edition. \i \link table.html Table Module\endlink \i \link workspace.html Workspace (MDI) Module\endlink \i \link xml.html XML Module\endlink -\i \link motif-extension.html TQMotif Extension\endlink \endlist */ diff --git a/doc/overviews-list.doc b/doc/overviews-list.doc index 7f60ebcd..75b511f7 100644 --- a/doc/overviews-list.doc +++ b/doc/overviews-list.doc @@ -94,7 +94,6 @@ \i \link eventsandfilters.html Events and Event Filters \endlink \i \link focus.html Keyboard Focus Overview \endlink \i \link accelerators.html Standard Accelerators \endlink - \i \link motif-extension.html Motif Support Extension \endlink \i \link opengl-x11-overlays.html OpenGL Overlays (X11)\endlink \i \link appicon.html Setting the Application Icon \endlink \i \link session.html Session Management \endlink @@ -105,7 +104,6 @@ \i \link timers.html Timers \endlink \i \link pictures.html Pictures of Most TQt Widgets \endlink \i \link distributingtqt.html Deploying TQt Applications\endlink -\omit \i \link xt.html TQt Xt/Motif Support Extension \endlink \endomit \endlist \endtable diff --git a/src/kernel/tqeventloop.cpp b/src/kernel/tqeventloop.cpp index 4cbd9899..3a7d7283 100644 --- a/src/kernel/tqeventloop.cpp +++ b/src/kernel/tqeventloop.cpp @@ -63,9 +63,7 @@ be delivered. TQEventLoop also allows the integration of an external event loop - with the TQt event loop. The Motif Extension included with TQt - includes a reimplementation of TQEventLoop for merging TQt and Motif - events together. + with the TQt event loop. To use your own instance of TQEventLoop or TQEventLoop subclass create it before you create the TQApplication object.