3 ms·
Thanks a lot for the explanation and the links, I'm going to go through all this. I think the signal/slot system of Qt is very well designed actually (I had no
by laurent123456 10y ago
Thanks a lot for the explanation and the links, I'm going to go through all this.
I think the signal/slot system of Qt is very well designed actually (I had no problem with it in pure C++ applications), it's just my implementation while using QML which ended up being messy. I also had to refactor some parts due to Android not liking slots in one thread and signal emitter in another. Also it seems signals were sent in a particular order on desktop and a different order on Android. That's why I'm looking for a clean architecture which would allow me to know and reason about what's happening in the application.
- nottorp 10y ago[quote] I also had to refactor some parts due to Android not liking slots in one thread and signal emitter in another. [/quote] Ouch? Worry free passing of signals/slots between threads is a feature of desktop Qt that I use and abuse all the time. I've even done a GUI-less daemon that used QtCore and abused signals/slots to communicate between threads. You mean it doesn't work on the mobile versions?