signals-slots

I have 3 objects(inherited from QObject ) that each contain a separate std::list . Each object gets created in the main gui thread (with no parent) and then is pushed to it's own thread (using Qt's QObject::moveToThread() ). Each thread is hooked up to a gui and messages are sent between the different threads with data. Each thread is to essentially handle it's own list. For example: Obj 1 : Consumer of data. It pop's the front off of its list(if data is present) to use. It also has a SLOT available so that other threads can push data to it. No other object can access this list directly only

I have a program that (amongst other things) has a command line interface that lets the user enter strings, which will then be sent over the network. The problem is that I'm not sure how to connect the events, which are generated deep inside the GUI, to the network interface. Suppose for instance that my GUI class hierarchy looks like this: GUI -> MainWindow -> CommandLineInterface -> EntryField Each GUI object holds some other GUI objects and everything is private. Now the entryField object generates an event/signal that a message has been entered. At the moment I'm passing the signal up the

I'm new in Qt and have a question. I have QLabel and QLineEdit objects, and when QLabel text is clicked on, I want to set this text in QLineEdit . Also I have read that QLabel has not clicked signal. Can you explain how can I do this and write code for me ?! Either style another type of QWidget such as a specific QPushButton to look like a QLabel and use its clicked() signal or inherit QLabel yourself and emit your own clicked() signal. See this example: https://wiki.qt.io/Clickable_QLabel If you choose the latter option you can pass the text in the signal. Then connect the necessary signals

Qt v4.8.0, VC2010 compiler I have a QMainWindow based class and I'm trying to send it signals involving QUuid However, every time I run it I get the errors: Object::connect: No such slot MainWindow::on_comp_connected(QUuid) in ..\..\src\mainwindow.cpp:143 Object::connect: (receiver name: 'MainWindow') It's driving me potty as the slot definitely does exist (it's in the moc_) class MainWindow : public QMainWindow { Q_OBJECT // SNIP private typedefs public: MainWindow(QWidget *parent = 0, Qt::WFlags flags = 0); ~MainWindow(); // SNIP public methods signals: void testSendQuuid(const QUuid &qcid);

QComboBox has two signals, both called currentIndexChanged ; one passes the index of the selected item, and the other passes the text of the selected item. When I connect this signal to my slot, with something like self.myComboBox.currentIndexChanged.connect(self.mySlot) it gives me an index. Is there a way I can use new-style signals to indicate that I want the text returned? Avaris See the second example in connecting signals portion of documentation. In your case it would be: self.myComboBox.currentIndexChanged[QtCore.QString].connect(self.mySlot) or if you are using v2 API for QString self

Let's say I have a ListView of clickable delegate components (or GridView or Repeater ). These delegate components need to emit a signal along with custom data when triggered that can be picked up by the parent of the ListView . How can this signal binding be achieved? e.g. The following code is my attempt but I don't know how to bind the trigger signal of the delegate component to the componentTriggered signal in the root item? Item { id: root anchors.fill: parent signal componentTriggered(string name) onComponentTriggered: { console.log(name + ' component was triggered') } ListModel { id:

I recently migrated my Qt project from Linux to Vista, and now I'm debugging signals blindly. On Linux, if QObject::connect() fails in a debug build, I get a warning message on stderr. On Windows, there is no console output for GUI applications, only an OutputDebugString call. I already installed DebugView , and it catches my own qDebug() output nicely, but still no warning on failed signals. One possible solution would be to use QtCreator's autocomplete for signals, but I like Eclipse, and using both is a PITA. Any ideas on how to get signal/slot info at runtime? Edit: I just realized connect

I have application that may benefit from using one of boost's signals libraries over a homegrown solution. The application is multithreaded but the part that does the signal processing is single threaded. Is there any reason to prefer Boost.Signals2 over Boost.Signal if multithreading is not an issue? Boost.Signals is now deprecated, and Boost.Signals2 should be used instead (see v1.54 docs ) Originally, if all the signals and slots were in the same thread, boost.signals was just fine. However, it is no longer being maintained -- the documentation suggests using signals2 in all new code. 来源：