@@ -146,6 +146,7 | |||||
146 | - QObject.emit to emit Qt signals from Python is not yet implemented but PythonQt allows to just emit a signal by calling it |
|
146 | - QObject.emit to emit Qt signals from Python is not yet implemented but PythonQt allows to just emit a signal by calling it | |
147 | - PythonQt does not (yet) offer to add new signals to Python/C++ objects |
|
147 | - PythonQt does not (yet) offer to add new signals to Python/C++ objects | |
148 | - Ownership of objects is a bit different in PythonQt, currently Python classes derived from a C++ class need to be manually referenced in Python to not get deleted too early (this will be fixed) |
|
148 | - Ownership of objects is a bit different in PythonQt, currently Python classes derived from a C++ class need to be manually referenced in Python to not get deleted too early (this will be fixed) | |
|
149 | - QString and QBytearray are always converted to unicode and str Python objects (PyQt returns QString and QByteArray instead). | |||
149 | - Probably there are lots of details that differ, I do not know PyQt that well to list them all. |
|
150 | - Probably there are lots of details that differ, I do not know PyQt that well to list them all. | |
150 |
|
151 | |||
151 | \section Interface |
|
152 | \section Interface |
General Comments 0
You need to be logged in to leave comments.
Login now