Language Bindings

@SGaist Thank you! :)

If you are trying to emit the signal selectedInfoChanged then you would do as follows: self.selectedInfoChanged.emit(packages, packagesSize, extraPackages, extraPackagesSize) If you are trying to declare a signal with that signature then you would do the following: class MyClass(QObject): selectedInfoChanged=pyqtSignal(int, str, int, str) Note: a signal must be a class attribute not an instance attribute and QString is not supported by PyQt5, just use python strings (PyQt5 automatically converts them to C++ QStrings). Hope this helps ;-)

found out! dropEvent() method of DragWidget() class needed to be modfied to get X and Y of dropped icon and pass those value to self.minimumSize() if newIcon.y()+32 > self.minimumHeight(): self.setMinimumHeight(newIcon.y()+32) if newIcon.x()+32 > self.minimumWidth(): self.setMinimumWidth(newIcon.x()+32)

Hi, PyQt is a library providing python Qt bindings for python, that means you can write python application with e.g. Qt GUI. QtScript is a (now deprecated) official module from Qt providing javascript style scripting capabilities that is replaced by the QtQml module. QtLua is a external Qt module written to provide Lua scripting capabilities to Qt applications. Hope it helps

It appears that at least one person is trying to resurrect PySide in a new github repo.

@Marine93 Well then you need a SortFilterProxyModel. It is based upon C++ QSortFilterProxyModel class. About the working you can find in this blog post. It shows for TableView but it will work for ListView too. Basically it will for those views which uses ListModel. You can find examples in Qt installed directory on your system too under quick directory.

Hi and welcome to devnet, For licensing related question, you should contact The Qt Company directly. You should find the licensing texts directly in the sources

@pyqtSlot( result = str ) is only for the C++ declaration. you can not use the return value with an emit Event. ;-( see http://stackoverflow.com/questions/11272951/pyqt4-pyqtslot-what-is-the-result-kwarg-for

Did you get any errors when you try to run it? The following works perfectly for me on Mac OSX 10.8, Python3.4, Qt5.4: test.qml import QtQuick 2.2 import QtQuick.Controls 1.1 ApplicationWindow{ width: 400 height: 300 visible: true title: qsTr("Hello") Label{ text: qsTr("Hello") anchors.centerIn: parent } } run.py from PyQt5.QtCore import * from PyQt5.QtGui import * from PyQt5.QtQml import * from sys import argv, exit def createApplication(): app=QGuiApplication(argv) engine=QQmlApplicationEngine(app) engine.load(QUrl("test.qml")) return app if __name__=="__main__": app=createApplication() exit(app.exec_()) To execute: $ python run.py

@alex111 Yes, that's right.

If you want make application with drag-and-drop, operating with DB, scripting to operate with widgets on the forms, store and load widgets in UI files, change forms without recompile of the project, take a look at QtRptDocumentDemo

What's weird is I tried the same code again today, but I'm getting the sender this time. Something is not right with how PySide passes the sender, but I can tell this is one of those bugs that will be really hard to track down since it's really inconsistent. Here's a simplified version of what I'm working with: import sys from PySide.QtCore import * from PySide.QtGui import * class CustomDialog(QDialog): def __init__(self, parent=None): super(CustomDialog, self).__init__(parent) self.setLayout(QVBoxLayout()) self.table = QTableWidget() self.table.setColumnCount(2) self.layout().addWidget(self.table) self.table.setRowCount(10) for row in xrange(self.table.rowCount()): item = QTableWidgetItem(str(row)) self.table.setItem(row, 0, item) combo = QComboBox() combo.addItems(['one', 'two', 'three']) combo.currentIndexChanged.connect(self.onIndexChanged) self.table.setCellWidget(row, 1, combo) @Slot(int) def onIndexChanged(self, index): print self.sender() def main(): app = QApplication(sys.argv) dialog = CustomDialog() dialog.show() app.exec_() if __name__ == '__main__': main() If you don't get the bug, I wouldn't spend too much time looking into it, but I appreciate the help.

Bump it on new forums... oh yeh

Is it really numpy.dot or could it also be numpy.zeros? I am allocating a huge 3d matrix via numpy.zeros and I seem to have a deadlock in some cases there too.