4 ms·
My own experience is with using QtWidgets in C++ for a multithreaded application that does some disk indexing and database management, the answer is "not that w
by Adverblessly 5y ago
My own experience is with using QtWidgets in C++ for a multithreaded application that does some disk indexing and database management, the answer is "not that well".
I found that the primitives for threading and message passing between threads didn't work that well for me (both in terms of what they provide and in terms of performance) so I ended up "bypassing" them a bit with my own threading code (that is, still using QThread and QMutex etc. but not using the signals and slots model).
Once I've done that and moved everything off of the main thread, things worked well, so that program is still in QtWidgets with C++ and still in use, but I felt that Qt didn't do a good job of making multithreading easy for me.
That said, I still like continue to use Qt so you can consider this a sort of mild endorsement from me, I guess.
- b20000 5y agoThat is what I expected. These frameworks look nice, but were often not created with typical real world scenarios in mind but only work well for very simple data in/out applications where performance doesn't matter.