More code snippets ported to Python.
This commit is contained in:
parent
11042fdbaa
commit
3798c8718c
18 changed files with 718 additions and 0 deletions
7
doc/extras/PySide.QtTest.rst
Normal file
7
doc/extras/PySide.QtTest.rst
Normal file
|
|
@ -0,0 +1,7 @@
|
|||
To include the definitions of the module's classes, use the following directive:
|
||||
|
||||
::
|
||||
|
||||
import PySide.QtTest
|
||||
|
||||
.. note:: All macros in the C++ version of QtTest were not binded in PySide, this module is useful only for GUI testing and benchmarking, for ordinary unit testing you should use the ``unittest`` Python module.
|
||||
9
doc/extras/PySide.QtUiTools.rst
Normal file
9
doc/extras/PySide.QtUiTools.rst
Normal file
|
|
@ -0,0 +1,9 @@
|
|||
These forms are processed at run-time to produce dynamically-generated user interfaces. In order to generate a form at run-time, a resource file containing a UI file is needed.
|
||||
|
||||
A form loader object, provided by the QUiLoader class, is used to construct the user interface. This user interface can be retrieved from any QIODevice; for example, a QFile object can be used to obtain a form stored in a project's resources. The :meth:`PySide.QtUiTools.QUiLoader.load` function takes the user interface description contained in the file and constructs the form widget.
|
||||
|
||||
To include the definitions of the module's classes, use the following directive:
|
||||
|
||||
::
|
||||
|
||||
import PySide..QtUiTools
|
||||
Loading…
Add table
Add a link
Reference in a new issue