From 16434e5519f6224e231bc5f7202f0e495eda7bb7 Mon Sep 17 00:00:00 2001 From: Slávek Banko Date: Tue, 3 Jan 2023 00:52:18 +0100 Subject: Do rename qt=>tqt on source files, directories and libraries. Rename pyuic=>pytquic, pylupdate=>pytqlupdate. Do rename qt=>tqt on constants and variables. Do rename QT=>TQT on constants. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Slávek Banko --- doc/tqtdocs.sip | 1915 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1915 insertions(+) create mode 100644 doc/tqtdocs.sip (limited to 'doc/tqtdocs.sip') diff --git a/doc/tqtdocs.sip b/doc/tqtdocs.sip new file mode 100644 index 0000000..5c8c295 --- /dev/null +++ b/doc/tqtdocs.sip @@ -0,0 +1,1915 @@ +// This is the SIP file for organising the PyTQt documentation. +// +// Copyright (c) 2007 +// Riverbank Computing Limited +// +// This file is part of PyTQt. +// +// This copy of PyTQt is free software; you can redistribute it and/or modify it +// under the terms of the GNU General Public License as published by the Free +// Software Foundation; either version 2, or (at your option) any later +// version. +// +// PyTQt is supplied in the hope that it will be useful, but WITHOUT ANY +// WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS +// FOR A PARTICULAR PURPOSE. See the GNU General Public License for more +// details. +// +// You should have received a copy of the GNU General Public License along with +// PyTQt; see the file LICENSE. If not, write to the Free Software Foundation, +// Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. + + +%Module Dummy + + +%Include tqt/versions.sip + + +%Doc + +
+ + Python Bindings for TQt (3.18.1) + + Phil + Thompson + + + + This document describes a set of Python bindings for the TQt widget set. + Contact the author at phil@riverbankcomputing.co.uk. + + + + + +Introduction + +PyTQt is a set of Python bindings for the TQt toolkit and available for all +platforms supported by TQt, including Windows, Linux, UNIX, MacOS/X and embedded +systems such as the Sharp Zaurus and the Compaq iPAQ. They have been tested +against TQt versions 1.43 to 3.3.6, TQt Non-commercial, TQtopia 1.5.0, and Python +versions 1.5 to 2.4.2. TQt/Embedded v3 is not supported. TQt v4 is supported +by PyTQt v4. + + + +PyTQt is available under the GPL license for use with the GPL version of TQt, a +a commercial license for use with the commercial version of TQt, a +non-commercial license for use with the non-commercial version of TQt v2, and an +educational license for use with the educational version of TQt. + + + +There is also an evaluation version of PyTQt for Windows. This must be used +with the corresponding evaluation version of TQt. + + + +PyTQt is built using SIP (a tool for generating Python extension modules for +C++ class libraries). SIP v4.6 or later must be installed in order to build +and run this version of PyTQt. + + + +PyTQt for MacOS/X requires TQt v3.1.0 or later and Python v2.3 or later. + + + +The bindings are implemented as a number of Python modules + + + + + +tqt is the main module and contains the core classes and most +user interface widgets. + + + + + +tqtaxcontainer contains a sub-set of the classes implemented +in TQt's TQAxContainer module, part of TQt's ActiveTQt framework. + + + + + +tqtcanvas contains the classes implemented in TQt's Canvas +module. + + + + + +tqtgl contains the classes implemented in TQt's OpenGL module. + + + + + +tqtnetwork contains the classes implemented in TQt's Network +module. + + + + + +tqtpe contains the classes implemented in TQtopia (originally +called the TQt Palmtop Environment). It is only supported with TQt/Embedded. + + + + + +tqtsql contains the classes implemented in TQt's SQL module. + + + + + +tqttable contains the classes implemented in TQt's Table +module. + + + + + +tqtui contains the classes implemented in TQt's tqui library. +These allow GUIs to be created directly from TQt Designer's +.ui files. + + + + + +tqtxml contains the classes implemented in TQt's XML module. + + + + + +tqtext contains useful third-party classes that are not part +of TQt. At the moment it contains bindings for TQScintilla, the port to TQt of +the Scintilla programmer's editor class. + + + + + +PyTQt also includes the pytquic and +pytqlupdate utilities which correspond to the TQt +uic and lupdate utilities. +pytquic converts the GUI designs created with TQt Designer to +executable Python code. pytqlupdate scans Python code, +extracts all strings that are candidates for internationalisation, and creates +an XML file for use by TQt Linguist. + + +Changes + +The changes visible to the Python programmer in this release are as follows. + + + + + +This version requires SIP v4.4 (or later). + + + + + +Concatenating Python strings and TQStrings is now supported. + + + + + +TQString now supports the * and +*= operators that behave as they do for Python strings. + + + + + +TQString is more interoperable with Python string and unicode +objects. For example they can be passed as arguments to +open() and to most (but not all) string methods. + + + + + +TQPopupMenu (and sub-classes) instances now transfer +ownership of the menu to Python in the call to exec_loop(). +This means the menu's resources are all released when the Python wrapper is +garbage collected without needing to call +TQObject.deleteLater(). + + + + + +TQObject.sender() now handles Python signals. + + + + + +The missing MacintoshVersion enum has been added. + + + + + +PYTQT_BUILD has been removed. + + + + + +The convention for converting between a C/C++ null pointer and Python's +None object has now been universally applied. In previous +versions a null pointer to, for example, a TQt list container would often be +converted to an empty list rather than None. + + + + + + + + +Other PyTQt Goodies +Using TQt Designer + +TQt Designer is a GPL'ed GUI design editor provided by Trolltech as part of TQt. +It generates an XML description of a GUI design. TQt includes +uic which generates C++ code from that XML. + + + +PyTQt includes pytquic which generates Python code from the +same XML. The Python code is self contained and can be executed immediately. + + + +It is sometimes useful to be able to include some specific Python code in the +output generated by pytquic. For example, if you are using +custom widgets, pytquic has no way of knowing the name of the +Python module containing the widget and so cannot generate the required +import statement. To help get around this, +pytquic will extract any lines entered in the +Comment field of TQt Designer's +Form Settings dialog that begin with +Python: and copies them to the generated output. + + + +Here's a simple example showing the contents of the Comment +field. + + + +This comment will be ignored by pytquic. +Python: +Python:# Import our custom widget. +Python:from foo import bar + + + +Here's the corresponding output from pytquic. + + + +from PyTQt.tqt import * + +# Import our custom widget. +from foo import bar + + + +Thanks to Christian Bird, pytquic will extract Python code +entered using TQt Designer to implement slots. In TQt Designer, when you need to +edit a slot and the source editor appears, enter Python code between the curly +braces. Don't worry about the correct starting indent level, each line is +prepended with a correct indentation. + + + +Make sure that the ui.h file is in the same directory as the +.ui file when using pytquic. The +.ui file implies the name of the .ui.h +file so there is no need to specify it on the command line. + + + +Here's an example of a simple slot. + + + +void DebMainWindowFrm::browsePushButtonClicked() +{ +if self.debugging: + TQMessageBox.critical(self, "Event", "browse pushbutton was clicked!") +} + + + +Here is the resulting code when pytquic is run. + + + +class DebMainWindowFrm(TQMainWindow): + ...stuff... + def browsePushButtonClicked(self): + if self.debugging: + TQMessageBox.critical(self, "Event", "browse pushbutton was clicked!") + + + +Note that indenting is as normal and that self and all other +parameters passed to the slot are available. + + + +If you use this, you will need to turn off all of the fancy options for the C++ +editor in Designer as it tries to force C++ syntax and that's naturally +annoying when trying to code in Python. + + + +Using TQt Linguist + +TQt includes the lupdate program which parses C++ source +files converting calls to the QT_TR_NOOP() and +QT_TRANSLATE_NOOP() macros to .ts +language source files. The lrelease program is then used to +generate .qm binary language files that are distributed with +your application. + + + +Thanks to Detlev Offenbach, PyTQt includes the pytqlupdate +program. This generates the same .ts language source files +from your PyTQt source files. + + + + + +Deploying Commercial PyTQt Applications + +When deploying commercial PyTQt applications it is necessary to discourage users +from accessing the underlying PyTQt modules for themselves. A user that used +the modules shipped with your application to develop new applications would +themselves be considered a developer and would need their own commercial TQt and +PyTQt licenses. + + + +One solution to this problem is the +VendorID +package. This allows you to build Python extension modules that can only be +imported by a digitally signed custom interpreter. The package enables you to +create such an interpreter with your application embedded within it. The +result is an interpreter that can only run your application, and PyTQt modules +that can only be imported by that interpreter. You can use the package to +similarly restrict access to any extension module. + + + +In order to build PyTQt with support for the VendorID package, pass the +-i command line flag to configure.py. + + + +<Literal>pytqtconfig</Literal> and Build System Support + +The SIP build system (ie. the sipconfig module) is described +in the SIP documentation. PyTQt includes the pytqtconfig +module that can be used by configuration scripts of other bindings that are +built on top of PyTQt. + + + +The pytqtconfig module contains the following classes: + + + + +Configuration(sipconfig.Configuration) + + +This class encapsulates additional configuration values, specific to PyTQt, that +can be accessed as instance variables. + + + +The following configuration values are provided (in addition to those provided +by the sipconfig.Configuration class): + + + + +pytqt_bin_dir + + +The name of the directory containing the pytquic and +pytqlupdate executables. + + + + + + +pytqt_config_args + + +The command line passed to configure.py when PyTQt was +configured. + + + + + + +pytqt_mod_dir + + +The name of the directory containing the PyTQt modules. + + + + + + +pytqt_modules + + +A string containing the names of the PyTQt modules that were installed. + + + + + + +pytqt_tqt_sip_flags + + +A string of the SIP flags used to generate the code for the +tqt module and which should be added to those needed by any +module that imports the tqt module. + + + + + + +pytqt_tqtaxcontainer_sip_flags + + +A string of the SIP flags used to generate the code for the +tqtaxcontainer module and which should be added to those +needed by any module that imports the tqtaxcontainer module. + + + + + + +pytqt_tqtcanvas_sip_flags + + +A string of the SIP flags used to generate the code for the +tqtcanvas module and which should be added to those needed by +any module that imports the tqtcanvas module. + + + + + + +pytqt_tqtext_sip_flags + + +A string of the SIP flags used to generate the code for the +tqtext module and which should be added to those needed by +any module that imports the tqtext module. + + + + + + +pytqt_tqtgl_sip_flags + + +A string of the SIP flags used to generate the code for the +tqtgl module and which should be added to those needed by any +module that imports the tqtgl module. + + + + + + +pytqt_tqtnetwork_sip_flags + + +A string of the SIP flags used to generate the code for the +tqtnetwork module and which should be added to those needed +by any module that imports the tqtnetwork module. + + + + + + +pytqt_tqtsql_sip_flags + + +A string of the SIP flags used to generate the code for the +tqtsql module and which should be added to those needed by +any module that imports the tqtsql module. + + + + + + +pytqt_tqttable_sip_flags + + +A string of the SIP flags used to generate the code for the +tqttable module and which should be added to those needed by +any module that imports the tqttable module. + + + + + + +pytqt_tqtui_sip_flags + + +A string of the SIP flags used to generate the code for the +tqtui module and which should be added to those needed by any +module that imports the tqtui module. + + + + + + +pytqt_tqtxml_sip_flags + + +A string of the SIP flags used to generate the code for the +tqtxml module and which should be added to those needed by +any module that imports the tqtxml module. + + + + + + +pytqt_sip_dir + + +The name of the base directory where the .sip files for each +of the PyTQt modules is installed. A sub-directory exists with the same name as +the module. + + + + + + +pytqt_version + + +The PyTQt version as a 3 part hexadecimal number (eg. v3.10 is represented as +0x030a00). + + + + + + +pytqt_version_str + + +The PyTQt version as a string. For development snapshots it will start with +snapshot-. + + + + + + + + + + +TQtModuleMakefile(sipconfig.SIPModuleMakefile) + + +The Makefile class for modules that import the tqt module. + + + +finalise(self) + + +This is a reimplementation of sipconfig.Makefile.finalise(). + + + + + + + + + +TQtAxContainerModuleMakefile(TQtModuleMakefile) + + +The Makefile class for modules that import the tqtaxcontainer +module. + + + +finalise(self) + + +This is a reimplementation of sipconfig.Makefile.finalise(). + + + + + + + + + +TQtCanvasModuleMakefile(TQtModuleMakefile) + + +The Makefile class for modules that import the tqtcanvas +module. + + + +finalise(self) + + +This is a reimplementation of sipconfig.Makefile.finalise(). + + + + + + + + + +TQtExtModuleMakefile(TQtModuleMakefile) + + +The Makefile class for modules that import the tqtext module. + + + +finalise(self) + + +This is a reimplementation of sipconfig.Makefile.finalise(). + + + + + + + + + +TQtGLModuleMakefile(TQtModuleMakefile) + + +The Makefile class for modules that import the tqtgl module. + + + +finalise(self) + + +This is a reimplementation of sipconfig.Makefile.finalise(). + + + + + + + + + +TQtNetworkModuleMakefile(TQtModuleMakefile) + + +The Makefile class for modules that import the tqtnetwork +module. + + + +finalise(self) + + +This is a reimplementation of sipconfig.Makefile.finalise(). + + + + + + + + + +TQtTableModuleMakefile(TQtModuleMakefile) + + +The Makefile class for modules that import the tqttable +module. + + + +finalise(self) + + +This is a reimplementation of sipconfig.Makefile.finalise(). + + + + + + + + + +TQtSQLModuleMakefile(TQtTableModuleMakefile) + + +The Makefile class for modules that import the tqtsql module. + + + +finalise(self) + + +This is a reimplementation of sipconfig.Makefile.finalise(). + + + + + + + + + +TQtUIModuleMakefile(TQtModuleMakefile) + + +The Makefile class for modules that import the tqtui module. + + + +finalise(self) + + +This is a reimplementation of sipconfig.Makefile.finalise(). + + + + + + + + + +TQtXMLModuleMakefile(TQtModuleMakefile) + + +The Makefile class for modules that import the tqtxml module. + + + +finalise(self) + + +This is a reimplementation of sipconfig.Makefile.finalise(). + + + + + + + + + + +%End + + +%ExportedDoc +Things to be Aware Of +super and Wrapped Classes + +Internally PyTQt implements a lazy technique for attribute lookup where +attributes are only placed in type and instance dictionaries when they are +first referenced. This technique is needed to reduce the time taken to import +large modules such as PyTQt. + + + +In most circumstances this technique is transparent to an application. The +exception is when super is used with a PyTQt class. The way +that super is currently implemented means that the lazy +lookup is bypassed resulting in AttributeError exceptions +unless the attribute has been previously referenced. + + + +Note that this restriction applies to any class wrapped by SIP and not just +PyTQt. + + + + +Python Strings, TQt Strings and Unicode + +Unicode support was added to TQt in v2.0 and to Python in v1.6. In TQt, Unicode +support is implemented using the TQString class. It is +important to understand that TQStrings, Python string objects +and Python Unicode objects are all different but conversions between them are +automatic in almost all cases and easy to achieve manually when needed. + + + +Whenever PyTQt expects a TQString as a function argument, a +Python string object or a Python Unicode object can be provided instead, and +PyTQt will do the necessary conversion automatically. + + + +You may also manually convert Python string and Unicode objects to +TQStrings by using the TQString constructor +as demonstrated in the following code fragment. + + + +qs1 = TQString('Converted Python string object') +qs2 = TQString(u'Converted Python Unicode object') + + + +In order to convert a TQString to a Python string object use +the Python str() function. Applying +str() to a null TQString and an empty +TQString both result in an empty Python string object. + + + +In order to convert a TQString to a Python Unicode object use +the Python unicode() function. Applying +unicode() to a null TQString and an empty +TQString both result in an empty Python Unicode object. + + + +Access to Protected Member Functions + +When an instance of a C++ class is not created from Python it is not possible +to access the protected member functions, or emit the signals, of that +instance. Attempts to do so will raise a Python exception. Also, any Python +methods corresponding to the instance's virtual member functions will never be +called. + + + +<Literal>None</Literal> and <Literal>NULL</Literal> + +Throughout the bindings, the None value can be specified +wherever NULL is acceptable to the underlying C++ code. + + + +Equally, NULL is converted to None +whenever it is returned by the underlying C++ code. + + + + +Support for C++ <Literal>void *</Literal> Data Types + +PyTQt represents void * values as objects of type +sip.voidptr. Such values are often used to pass the +addresses of external objects between different Python modules. To make this +easier, a Python integer (or anything that Python can convert to an integer) +can be used whenever a sip.voidptr is expected. + + +A sip.voidptr may be converted to a Python integer by using +the int() builtin function. + + +A sip.voidptr may be converted to a Python string by using +its asstring() method. The asstring() +method takes an integer argument which is the length of the data in bytes. + + + + +Support for Threads + +PyTQt implements the full set of TQt's thread classes. Python, of course, also +has its own thread extension modules. If you are using SIP v4 (or later) and +Python v2.3.5 (or later) then PyTQt does not impose any additional restrictions. +(Read the relevant part of the TQt documentation to understand the restrictions +imposed by the TQt API.) + + +If you are using earlier versions of either SIP or Python then it is possible +to use either of the APIs so long as you follow some simple rules. + + + + +If you use the TQt API then the very first import of one of +the PyTQt modules must be done from the main thread. + + + + +If you use the Python API then all calls to PyTQt (including any +imports) must be done from one thread only. Therefore, if +you want to make calls to PyTQt from several threads then you must use the TQt +API. + + + + +If you want to use both APIs in the same application then all calls to PyTQt +must be done from threads created using the TQt API. + + + + +The above comments actually apply to any SIP generated module, not just PyTQt. + + + +Garbage Collection + +C++ does not garbage collect unreferenced class instances, whereas Python does. +In the following C++ fragment both colours exist even though the first can no +longer be referenced from within the program: + + + +c = new TQColor(); +c = new TQColor(); + + + +In the corresponding Python fragment, the first colour is destroyed when +the second is assigned to c: + + + +c = TQColor() +c = TQColor() + + + +In Python, each colour must be assigned to different names. Typically this +is done within class definitions, so the code fragment would be something like: + + + +self.c1 = TQColor() +self.c2 = TQColor() + + + +Sometimes a TQt class instance will maintain a pointer to another instance and +will eventually call the destructor of that second instance. The most common +example is that a TQObject (and any of its sub-classes) keeps +pointers to its children and will automatically call their destructors. In +these cases, the corresponding Python object will also keep a reference to the +corresponding child objects. + + + +So, in the following Python fragment, the first TQLabel is +not destroyed when the second is assigned to l because the +parent TQWidget still has a reference to it. + + + +p = TQWidget() +l = TQLabel('First label',p) +l = TQLabel('Second label',p) + + + +C++ Variables + +Access to C++ variables is supported. They are accessed as Python instance +variables. For example: + + + +tab = TQTab() +tab.label = "First Tab" +tab.r = TQRect(10,10,75,30) + + + +Global variables and static class variables are effectively read-only. They +can be assigned to, but the underlying C++ variable will not be changed. This +may change in the future. + + + +Access to protected C++ class variables is not supported. This may change in +the future. + + + +Multiple Inheritance + +It is not possible to define a new Python class that sub-classes from more than +one TQt class. + + + +i18n Support + +TQt implements i18n support through the TQt Linguist application, the +TQTranslator class, and the +TQApplication::translate(), TQObject::tr() +and TQObject::trUtf8() methods. Usually the +tr() method is used to obtain the correct translation of a +message. The translation process uses a message context to allow the same +message to be translated differently. tr() is actually +generated by moc and uses the hardcoded class name as the +context. On the other hand, TQApplication::translate() +allows to context to be explicitly stated. + + + +Unfortunately, because of the way TQt implents tr() (and +trUtf8()) it is not possible for PyTQt to exactly reproduce +its behavour. The PyTQt implementation of tr() (and +trUtf8()) uses the class name of the instance as the +context. The key difference, and the source of potential problems, is that the +context is determined dynamically in PyTQt, but is hardcoded in TQt. In other +words, the context of a translation may change depending on an instance's class +hierarchy. + + + +class A(TQObject): + def __init__(self): + TQObject.__init__(self) + + def hello(self): + return self.tr("Hello") + +class B(A): + def __init__(self): + A.__init__(self) + +a = A() +a.hello() + +b = B() +b.hello() + + + +In the above the message is translated by a.hello() using a +context of A, and by b.hello() using a +context of B. In the equivalent C++ version the context +would be A in both cases. + + + +The PyTQt behaviour is unsatisfactory and may be changed in the future. It is +recommended that TQApplication.translate() be used in +preference to tr() (and trUtf8()). This +is guaranteed to work with current and future versions of PyTQt and makes it +much easier to share message files between Python and C++ code. Below is the +alternative implementation of A that uses +TQApplication.translate(). + + + +class A(TQObject): + def __init__(self): + TQObject.__init__(self) + + def hello(self): + return tqApp.translate("A","Hello") + + + +Note that the code generated by pytquic uses +TQApplication.translate(). + + + + + +Signal and Slot Support + +A signal may be either a TQt signal (specified using +SIGNAL()) or a Python signal (specified using +PYSIGNAL()). + + + +A slot can be either a Python callable object, a TQt signal (specified using +SIGNAL()), a Python signal (specified using +PYSIGNAL()), or a TQt slot (specified using +SLOT()). + + + +You connect signals to slots (and other signals) as you would from C++. For +example: + + + +TQObject.connect(a,SIGNAL("TQtSig()"),pyFunction) +TQObject.connect(a,SIGNAL("TQtSig()"),pyClass.pyMethod) +TQObject.connect(a,SIGNAL("TQtSig()"),PYSIGNAL("PySig")) +TQObject.connect(a,SIGNAL("TQtSig()"),SLOT("TQtSlot()")) +TQObject.connect(a,PYSIGNAL("PySig"),pyFunction) +TQObject.connect(a,PYSIGNAL("PySig"),pyClass.pyMethod) +TQObject.connect(a,PYSIGNAL("PySig"),SIGNAL("TQtSig()")) +TQObject.connect(a,PYSIGNAL("PySig"),SLOT("TQtSlot()")) + + + +When a slot is a Python method that corresponds to a TQt slot then a signal can +be connected to either the Python method or the TQt slot. The following +connections achieve the same effect. + + + +sbar = TQScrollBar() +lcd = TQLCDNumber() + +TQObject.connect(sbar,SIGNAL("valueChanged(int)"),lcd.display) +TQObject.connect(sbar,SIGNAL("valueChanged(int)"),lcd,SLOT("display(int)")) + + + +The difference is that the second connection is made at the C++ level and is +more efficient. + + + +Disconnecting signals works in exactly the same way. + + + +Any instance of a class that is derived from the TQObject +class can emit a signal using the emit method. This takes +two arguments. The first is the Python or TQt signal, the second is a Python +tuple which are the arguments to the signal. For example: + + + +a.emit(SIGNAL("clicked()"),()) +a.emit(PYSIGNAL("pySig"),("Hello","World")) + + + +Note that when a slot is a Python callable object its reference count is not +increased. This means that a class instance can be deleted without having to +explicitly disconnect any signals connected to its methods. However, it also +means that using lambda expressions as slots will not work unless you keep a +separate reference to the expression to prevent it from being immediately +garbage collected. + + + +TQt allows a signal to be connected to a slot that requires fewer arguments than +the signal passes. The extra arguments are quietly discarded. Python slots +can be used in the same way. + + + + +Static Member Functions + +Static member functions are implemented as Python class functions. +For example the C++ static member function +TQObject::connect() is called from Python as +TQObject.connect() or self.connect() if +called from a sub-class of TQObject. + + + + +Enumerated Types + +Enumerated types are implemented as a set of simple variables corresponding to +the separate enumerated values. + + + +When using an enumerated value the name of the class (or a sub-class) in which +the enumerated type was defined in must be included. For example: + + + +TQt.SolidPattern +TQWidget.TabFocus +TQFrame.TabFocus + + + + +Module Reference Documentation + +The following sections should be used in conjunction with the normal class +documentation - only the differences specific to the Python bindings are +documented here. + + + +In these sections, Not yet implemented +implies that the feature can be easily implemented if needed. Not +implemented implies that the feature will not be implemented, either +because it cannot be or because it is not appropriate. + + + +If a class is described as being fully implemented then +all non-private member functions and all public class variables have been +implemented. + + + +If an operator has been implemented then it is stated explicitly. + + + +Classes that are not mentioned have not yet been implemented. + + + + +<Literal>tqt</Literal> Module Reference +%End + +%Include tqt/tqglobal.sip +%Include tqt/tqwindowdefs.sip +%Include tqt/tqnamespace.sip + +%Include tqt/tqaccel.sip +%Include tqt/tqaction.sip +%Include tqt/tqapplication.sip +%Include tqt/tqassistantclient.sip +%Include tqt/tqbitmap.sip +%Include tqt/tqbrush.sip +%Include tqt/tqbutton.sip +%Include tqt/tqbuttongroup.sip +%Include tqt/tqbytearray.sip +%Include tqt/tqcdestyle.sip +%Include tqt/tqcheckbox.sip +%Include tqt/tqclipboard.sip +%Include tqt/tqcolor.sip +%Include tqt/tqcolordialog.sip +%Include tqt/tqcolorgroup.sip +%Include tqt/tqcombobox.sip +%Include tqt/tqcommonstyle.sip +%Include tqt/tqcstring.sip +%Include tqt/tqcursor.sip +%Include tqt/tqdatastream.sip +%Include tqt/tqdatetime.sip +%Include tqt/tqdatetimeedit.sip +%Include tqt/tqdesktopwidget.sip +%Include tqt/tqdial.sip +%Include tqt/tqdialog.sip +%Include tqt/tqdir.sip +%Include tqt/tqdockarea.sip +%Include tqt/tqdockwindow.sip +%Include tqt/tqdragobject.sip +%Include tqt/tqdrawutil.sip +%Include tqt/tqdropsite.sip +%Include tqt/tqerrormessage.sip +%Include tqt/tqevent.sip +%Include tqt/tqeventloop.sip +%Include tqt/tqfile.sip +%Include tqt/tqfiledialog.sip +%Include tqt/tqfileinfo.sip +%Include tqt/tqfont.sip +%Include tqt/tqfontdatabase.sip +%Include tqt/tqfontdialog.sip +%Include tqt/tqfontinfo.sip +%Include tqt/tqfontmetrics.sip +%Include tqt/tqframe.sip +%Include tqt/tqgrid.sip +%Include tqt/tqgridview.sip +%Include tqt/tqgroupbox.sip +%Include tqt/tqhbox.sip +%Include tqt/tqhbuttongroup.sip +%Include tqt/tqheader.sip +%Include tqt/tqhgroupbox.sip +%Include tqt/tqiconset.sip +%Include tqt/tqiconview.sip +%Include tqt/tqimage.sip +%Include tqt/tqinputdialog.sip +%Include tqt/tqinterlacestyle.sip +%Include tqt/tqiodevice.sip +%Include tqt/tqkeysequence.sip +%Include tqt/tqlabel.sip +%Include tqt/tqlayout.sip +%Include tqt/tqlcdnumber.sip +%Include tqt/tqlibrary.sip +%Include tqt/tqlineedit.sip +%Include tqt/tqlistbox.sip +%Include tqt/tqlistview.sip +%Include tqt/tqlocale.sip +%Include tqt/tqmainwindow.sip +%Include tqt/tqmemarray.sip +%Include tqt/tqmenubar.sip +%Include tqt/tqmenudata.sip +%Include tqt/tqmessagebox.sip +%Include tqt/tqmetaobject.sip +%Include tqt/tqmime.sip +%Include tqt/tqmotifplusstyle.sip +%Include tqt/tqmotifstyle.sip +%Include tqt/tqmovie.sip +%Include tqt/tqmultilinedit.sip +%Include tqt/tqmutex.sip +%Include tqt/tqnetworkprotocol.sip +%Include tqt/tqobject.sip +%Include tqt/tqobjectcleanuphandler.sip +%Include tqt/tqobjectlist.sip +%Include tqt/tqpaintdevicemetrics.sip +%Include tqt/tqpaintdevice.sip +%Include tqt/tqpainter.sip +%Include tqt/tqpalette.sip +%Include tqt/tqpixmap.sip +%Include tqt/tqpixmapcache.sip +%Include tqt/tqpair.sip +%Include tqt/tqpen.sip +%Include tqt/tqpicture.sip +%Include tqt/tqplatinumstyle.sip +%Include tqt/tqpoint.sip +%Include tqt/tqpointarray.sip +%Include tqt/tqpopupmenu.sip +%Include tqt/tqprintdialog.sip +%Include tqt/tqprinter.sip +%Include tqt/tqprocess.sip +%Include tqt/tqprogressbar.sip +%Include tqt/tqprogressdialog.sip +%Include tqt/tqptrlist.sip +%Include tqt/tqpushbutton.sip +%Include tqt/tqradiobutton.sip +%Include tqt/tqrangecontrol.sip +%Include tqt/tqrect.sip +%Include tqt/tqregexp.sip +%Include tqt/tqregion.sip +%Include tqt/tqscrollbar.sip +%Include tqt/tqscrollview.sip +%Include tqt/tqsemaphore.sip +%Include tqt/tqsemimodal.sip +%Include tqt/tqsessionmanager.sip +%Include tqt/tqsettings.sip +%Include tqt/tqsgistyle.sip +%Include tqt/tqsignalmapper.sip +%Include tqt/tqsimplerichtext.sip +%Include tqt/tqsize.sip +%Include tqt/tqsizegrip.sip +%Include tqt/tqsizepolicy.sip +%Include tqt/tqslider.sip +%Include tqt/tqsocketnotifier.sip +%Include tqt/tqsound.sip +%Include tqt/tqspinbox.sip +%Include tqt/tqsplashscreen.sip +%Include tqt/tqsplitter.sip +%Include tqt/tqstatusbar.sip +%Include tqt/tqstring.sip +%Include tqt/tqstringlist.sip +%Include tqt/tqstrlist.sip +%Include tqt/tqstyle.sip +%Include tqt/tqstylesheet.sip +%Include tqt/tqsyntaxhighlighter.sip +%Include tqt/tqtabbar.sip +%Include tqt/tqtabdialog.sip +%Include tqt/tqtabwidget.sip +%Include tqt/tqtextbrowser.sip +%Include tqt/tqtextcodec.sip +%Include tqt/tqtextedit.sip +%Include tqt/tqtextstream.sip +%Include tqt/tqtextview.sip +%Include tqt/tqthread.sip +%Include tqt/tqtimer.sip +%Include tqt/tqtoolbar.sip +%Include tqt/tqtoolbox.sip +%Include tqt/tqtoolbutton.sip +%Include tqt/tqtooltip.sip +%Include tqt/tqtranslator.sip +%Include tqt/tqurl.sip +%Include tqt/tqurlinfo.sip +%Include tqt/tqurloperator.sip +%Include tqt/tquuid.sip +%Include tqt/tqvalidator.sip +%Include tqt/tqvaluelist.sip +%Include tqt/tqvariant.sip +%Include tqt/tqvbox.sip +%Include tqt/tqvbuttongroup.sip +%Include tqt/tqvgroupbox.sip +%Include tqt/tqwaitcondition.sip +%Include tqt/tqwhatsthis.sip +%Include tqt/tqwidget.sip +%Include tqt/tqwidgetlist.sip +%Include tqt/tqwidgetstack.sip +%Include tqt/tqwindowsstyle.sip +%Include tqt/tqwindowsxpstyle.sip +%Include tqt/tqwizard.sip +%Include tqt/tqwmatrix.sip +%Include tqt/tqworkspace.sip + +%ExportedDoc + +%End + + +%ExportedDoc +<Literal>tqtaxcontainer</Literal> Module Reference +%End + +%Include tqtaxcontainer/tqaxbase.sip +%Include tqtaxcontainer/tqaxobject.sip +%Include tqtaxcontainer/tqaxwidget.sip + +%ExportedDoc + +%End + + +%ExportedDoc +<Literal>tqtcanvas</Literal> Module Reference +%End + +%Include tqtcanvas/tqcanvas.sip + +%ExportedDoc + +%End + + +%ExportedDoc +<Literal>tqtext</Literal> Module Reference + +TQextScintilla + + void getCursorPosition + int *line + int *index + + +This takes no parameters and returns a tuple of the values returned by the +line and index pointers. + + + + void getSelection + int *lineFrom + int *indexFrom + int *lineTo + int *indexTo + + +This takes no parameters and returns a tuple of the values returned by the +lineFrom, indexFrom, +lineTo and indexTo pointers. + + + +TQextScintillaAPIs + +TQextScintillaAPIs is fully implemented. + + + +TQextScintillaBase + +TQextScintillaBase is fully implemented. + + + +TQextScintillaCommand + +TQextScintillaCommand is fully implemented. + + + +TQextScintillaCommandSet + +TQextScintillaCommandSet is fully implemented. + + + +TQextScintillaDocument + +TQextScintillaDocument is fully implemented. + + + +TQextScintillaLexer + +TQextScintillaLexer is fully implemented. + + + +TQextScintillaLexerBash (TQScintilla v1.4+) + +TQextScintillaLexerBash is fully implemented. + + + +TQextScintillaLexerBatch (TQScintilla v1.6+) + +TQextScintillaLexerBatch is fully implemented. + + + +TQextScintillaLexerCPP + +TQextScintillaLexerCPP is fully implemented. + + + +TQextScintillaLexerCSharp + +TQextScintillaLexerCSharp is fully implemented. + + + +TQextScintillaLexerCSS (TQScintilla v1.6+) + +TQextScintillaLexerCSS is fully implemented. + + + +TQextScintillaLexerDiff (TQScintilla v1.6+) + +TQextScintillaLexerDiff is fully implemented. + + + +TQextScintillaLexerHTML (TQScintilla v1.1+) + +TQextScintillaLexerHTML is fully implemented. + + + +TQextScintillaLexerIDL + +TQextScintillaLexerIDL is fully implemented. + + + +TQextScintillaLexerJava + +TQextScintillaLexerJava is fully implemented. + + + +TQextScintillaLexerJavaScript + +TQextScintillaLexerJavaScript is fully implemented. + + + +TQextScintillaLexerLua (TQScintilla v1.5+) + +TQextScintillaLexerLua is fully implemented. + + + +TQextScintillaLexerMakefile (TQScintilla v1.6+) + +TQextScintillaLexerMakefile is fully implemented. + + + +TQextScintillaLexerPerl + +TQextScintillaLexerPerl is fully implemented. + + + +TQextScintillaLexerPOV (TQScintilla v1.6+) + +TQextScintillaLexerPOV is fully implemented. + + + +TQextScintillaLexerProperties (TQScintilla v1.6+) + +TQextScintillaLexerProperties is fully implemented. + + + +TQextScintillaLexerPython + +TQextScintillaLexerPython is fully implemented. + + + +TQextScintillaLexerRuby (TQScintilla v1.5+) + +TQextScintillaLexerRuby is fully implemented. + + + +TQextScintillaLexerSQL (TQScintilla v1.1+) + +TQextScintillaLexerSQL is fully implemented. + + + +TQextScintillaLexerTeX (TQScintilla v1.6+) + +TQextScintillaLexerTeX is fully implemented. + + + +TQextScintillaMacro + +TQextScintillaMacro is fully implemented. + + + +TQextScintillaPrinter + +TQextScintillaPrinter is fully implemented. + + +%End + + +%ExportedDoc + +%End + + +%ExportedDoc +<Literal>tqtgl</Literal> Module Reference +%End + +%Include tqtgl/tqgl.sip +%Include tqtgl/tqglcolormap.sip + +%ExportedDoc + +%End + + +%ExportedDoc +<Literal>tqtnetwork</Literal> Module Reference +%End + +%Include tqtnetwork/tqdns.sip +%Include tqtnetwork/tqftp.sip +%Include tqtnetwork/tqhostaddress.sip +%Include tqtnetwork/tqhttp.sip +%Include tqtnetwork/tqlocalfs.sip +%Include tqtnetwork/tqnetwork.sip +%Include tqtnetwork/tqserversocket.sip +%Include tqtnetwork/tqsocket.sip +%Include tqtnetwork/tqsocketdevice.sip + +%ExportedDoc + +%End + + +%ExportedDoc +<Literal>tqtpe</Literal> Module Reference + +TQPEApplication + + TQApplication + int& argc + char **argv + Type type + + +This takes two parameters, the first of which is a list of argument strings. +Arguments used by TQt are removed from the list. + + + + int exec + + + +This has been renamed to exec_loop in Python. + + + +AppLnk + + virtual TQString exec const + + + +This has been renamed to exec_property in Python. + + + +AppLnkSet + +AppLnkSet is fully implemented. + + + +Config + +Config is fully implemented. + + + +DateFormat + +DateFormat is fully implemented. + + + +DocLnk + + TQString exec const + + + +This has been renamed to exec_property in Python. + + + +DocLnkSet + +DocLnkSet is fully implemented. + + + +FileManager + +FileManager is fully implemented. + + + +FileSelector + +FileSelector is fully implemented. + + + +FileSelectorItem + +FileSelectorItem is fully implemented. + + + +FontDatabase + +FontDatabase is fully implemented. + + + +Global + + static void setBuiltinCommands + Command * + + +Not implemented. + + + +MenuButton + +MenuButton is fully implemented. + + + +TQCopEnvelope + +TQCopEnvelope is fully implemented. + + + +TQDawg + +TQDawg is fully implemented. + + + +TQPEMenuBar + +TQPEMenuBar is fully implemented. + + + +TQPEToolBar + +TQPEToolBar is fully implemented. + + + +Resource + +Resource is fully implemented. + + + + +%End + + +%ExportedDoc +<Literal>tqtsql</Literal> Module Reference +%End + +%Include tqtsql/tqdatabrowser.sip +%Include tqtsql/tqdatatable.sip +%Include tqtsql/tqdataview.sip +%Include tqtsql/tqeditorfactory.sip +%Include tqtsql/tqsql.sip +%Include tqtsql/tqsqlcursor.sip +%Include tqtsql/tqsqldatabase.sip +%Include tqtsql/tqsqldriver.sip +%Include tqtsql/tqsqleditorfactory.sip +%Include tqtsql/tqsqlerror.sip +%Include tqtsql/tqsqlfield.sip +%Include tqtsql/tqsqlform.sip +%Include tqtsql/tqsqlindex.sip +%Include tqtsql/tqsqlpropertymap.sip +%Include tqtsql/tqsqlquery.sip +%Include tqtsql/tqsqlrecord.sip +%Include tqtsql/tqsqlresult.sip +%Include tqtsql/tqsqlselectcursor.sip + +%ExportedDoc + +%End + + +%ExportedDoc +<Literal>tqttable</Literal> Module Reference +%End + +%Include tqttable/tqtable.sip + +%ExportedDoc + +%End + + +%ExportedDoc +<Literal>tqtui</Literal> Module Reference +%End + +%Include tqtui/tqwidgetfactory.sip + +%ExportedDoc + +%End + + +%ExportedDoc +<Literal>tqtxml</Literal> Module Reference +%End + +%Include tqtxml/tqdom.sip + +%ExportedDoc + +%End + + +%Doc +
+%End -- cgit v1.2.3