signals-slots

Is it possible to see definition of Q_SIGNALS, Q_SLOT, SLOT(), SIGNAL() macros in Qt framework? P.S. Google gave me nothing in this question. Form qobjectdefs.h , for a non-debug compilation: #define Q_SLOTS #define Q_SIGNALS protected #define SLOT(a) "1"#a #define SIGNAL(a) "2"#a The Q_SLOTS and Q_SIGNALS declarations are only treated specially by the moc run, in the final compilation they reduce to simple method declarations. SIGNAL() and SLOT() create names from the provided signatures. With visual studio - right click the identifier you're interested in and choose "Go To Definition" or

I would like to know what are the consequences of emitting a signal from a regular python thread within a QObject, compared with a QThread. See the following class: class MyObject(QtCore.QObject): def __init__(self): super().__init__() sig = pyqtSignal() def start(self): self._thread = Thread(target=self.run) self._thread.start() def run(self): self.sig.emit() # Do something Now, assuming that in the GUI thread, I have: def __init__(self): self.obj = MyObject() self.obj.sig.connect(self.slot) self.obj.start() def slot(self): # Do something the slot is indeed executed when the signal is emitted

I am new to QT and I am doing some learning. I would like to trigger a slot that modify a GUI widget from a C++ thread(Currently a Qthread). Unfortunatly I get a: ASSERTION failed at: Q_ASSERT(qApp && qApp->thread() == QThread::currentThread()); here is some code: (MAIN + Thread class) class mythread : public QThread { public: mythread(mywindow* win){this->w = win;}; mywindow* w; void run() { w->ui.textEdit->append("Hello"); //<--ASSERT FAIL //I have also try to call a slots within mywindow which also fail. }; }; int main(int argc, char *argv[]) { QApplication* a = new QApplication(argc, argv)

Connecting a QML signal to a regular C++ slot is easy: // QML Rectangle { signal foo(); } // C++ old-style QObject::connect(some_qml_container, SIGNAL(foo()), some_qobject, SLOT(fooSlot()); // works! However, no matter what I try, I cannot seem to be able to connect to a C++11 lambda function slot. // C++11 QObject::connect(some_qml_container, SIGNAL(foo()), [=]() { /* response */ }); // fails... QObject::connect(some_qml_container, "foo()", [=]() { /* response */ }); // fails... Both attempts fail with a function signature error (no QObject::connect overload can accept these parameters).

Where are the signals itemChecked and itemUncheсked on the QTreeWidget ? Qt Signals: (quote from PyQt4 QTreeWidget documentation page) void currentItemChanged (QTreeWidgetItem *,QTreeWidgetItem *) void itemActivated (QTreeWidgetItem *,int) void itemChanged (QTreeWidgetItem *,int) void itemClicked (QTreeWidgetItem *,int) void itemCollapsed (QTreeWidgetItem *) void itemDoubleClicked (QTreeWidgetItem *,int) void itemEntered (QTreeWidgetItem *,int) void itemExpanded (QTreeWidgetItem *) void itemPressed (QTreeWidgetItem *,int) void itemSelectionChanged () At current moment I solved it like this:

I am developing an application using python and Qt. I have designed 2 Main windows ie..QMainWindow (Not QWidget or QDialog) using Qt. Let it be. 1.LoginWindow -- LoginUI(Qt) 2.StuffWindow --- StuffUI First i should display Login Window. Then i should pass the username to StaffWindow (username needed for managing stuffs) StaffWindow should be shown and LoginWindow Should be Closed.. How can i achieve this..? Help me.. Regardless of your description, I think your LoginWindow should be a QDialog, and your StuffWIndow be the MainWindow, and function like this... Your StuffWindow MainWindow should

I'm using pyqt5, and I have several methods connected using code similar to the following: self.progress.canceled.connect(self.cancel) Where, for example, self.cancel is: def cancel(self): self.timer.stop() This code seems to work cleanly in multiple scenarios, without ever decorating cancel with pyqtSlot or doing anything special with it. My questions are: What am I losing by doing it this way? What is the reason pyqtSlot is required? ekhumoro The main purpose of pyqtSlot is to allow several different overloads of a slot to be defined, each with a different signature. It may also be needed