2020腾讯云限时秒杀，爆款1核2G云服务器99元/年！（领取2860元代金券），
地址：https://cloud.tencent.com/act/cps/redirect?redirect=1062
2020阿里云最低价产品入口+领取代金券(老用户3折起)，
入口地址：https://www.aliyun.com/minisite/goods
SOLVED Cross-Thread signal: Cannot queue arguments of type 'QVector This topic has been deleted. Only users with topic management privileges can see it. The Qt D-Busmodule is a Unix-only library you can use to implement IPC using the D-Bus protocol.
Qt documentation states that signals and slots can be direct, queued and auto.
It also stated that if object that owns slot 'lives' in a thread different from object that owns signal, emitting such signal will be like posting message - signal emit will return instantly and slot method will be called in target thread's event loop.
Unfortunately, documentation do not specify that 'lives' stands for and no examples is available. I have tried the following code:
main.h:
main.cpp:
Output is:
MySlot() is never called :(. What I'm doing wrong?
Recommend：c++ - Signals and Slots help QT
ss lets say test. in the ui function i need to connect my signal and slot but im trying the code from the QT docs and having no luck signal declaration signals:void paint(int x, int y, int id); signal emit emit paint(x, y, id) connectio
answer 1 >>---Accepted---Accepted---Accepted---
There are quite a few problems with your code :
- like said by Evan the emit keyword is missing
- all your objects live in the main thread, only the code in the run methods live in other threads, which means that the MySlot slot would be called in the main thread and I'm not sure that's what you want
- your slot will never be called since the main event loop will never been launched : your two calls to wait() will only timeout after a very long time (and you'll probably kill your application before that happens) and I don't think that's what you want either, anyway they really have no use in your code.
This code would most likely work (though I have not tested it) and I think it does what you want it to do :
Now MyObject will live in thread2 (thanks to moveToThread).
MySignal should be sent from thread1 (thought I'm not sure on that one, it might be sent from main thread, it doesn't really matter).
No event loop is needed in thread1 since emitting a signal doesn't need an event loop. An event loop is needed in thread2 (lanched by exec()) to receive the signal.
MySlot will be called in thread2.
Recommend：c++ - How to create dynamic signals and slots in Qt
ed by the moc compiler. Now I want to create signals and slots dynamically at run-time. I already have a working solution, but it feels to me like a hack, although I am using publicly available methods. This is the code for dynamic slots: b
2020腾讯云限时秒杀，爆款1核2G云服务器99元/年！（领取2860元代金券），
地址：https://cloud.tencent.com/act/cps/redirect?redirect=1062
2020阿里云最低价产品入口+领取代金券(老用户3折起)，
入口地址：https://www.aliyun.com/minisite/goods
Qt documentation states that signals and slots can be direct, queued and auto.
It also stated that if object that owns slot 'lives' in a thread different from object that owns signal, emitting such signal will be like posting message - signal emit will return instantly and slot method will be called in target thread's event loop.
Unfortunately, documentation do not specify that 'lives' stands for and no examples is available. I have tried the following code:
main.h:
main.cpp:
Output is:
MySlot() is never called :(. What I'm doing wrong?
Qt Signal Thread
Recommend：c++ - Signals and Slots help QT
ss lets say test. in the ui function i need to connect my signal and slot but im trying the code from the QT docs and having no luck signal declaration signals:void paint(int x, int y, int id); signal emit emit paint(x, y, id) connectio
answer 1 >>---Accepted---Accepted---Accepted---
There are quite a few problems with your code :
- like said by Evan the emit keyword is missing
- all your objects live in the main thread, only the code in the run methods live in other threads, which means that the MySlot slot would be called in the main thread and I'm not sure that's what you want
- your slot will never be called since the main event loop will never been launched : your two calls to wait() will only timeout after a very long time (and you'll probably kill your application before that happens) and I don't think that's what you want either, anyway they really have no use in your code.
Qt Connect Signal Slot
This code would most likely work (though I have not tested it) and I think it does what you want it to do :
Now MyObject will live in thread2 (thanks to moveToThread).
MySignal should be sent from thread1 (thought I'm not sure on that one, it might be sent from main thread, it doesn't really matter).
No event loop is needed in thread1 since emitting a signal doesn't need an event loop. An event loop is needed in thread2 (lanched by exec()) to receive the signal.
MySlot will be called in thread2.
Recommend：c++ - How to create dynamic signals and slots in Qt
Qt Cross Thread Signal Slotted
ed by the moc compiler. Now I want to create signals and slots dynamically at run-time. I already have a working solution, but it feels to me like a hack, although I am using publicly available methods. This is the code for dynamic slots: b