I've watched a couple of videos and they are pretty good.
In fact, they are better than most of the eLearning videos of Nokia. Yesterday I sent a comment to Nokia that they should use native english speakers or at least put subtitles on their videos because the audio is bad and the speakers are hard to understand.
You seem to be a native english speaker? Your videos are much more comfortable to listen to.
Now some comments on the videos explaining QThread.
I don't know if you know this, but the QThread object uses the main event loop.
In part 4, you got away by not using slots :-)
Signals usually are not the problem, but slots in another thread are. You must have an event loop running in your thread. And you must make sure that the slot code is executed inside the thread. Otherwise strange problems occur. Recently, someone here on this forum created a multi threaded client/server application and got synchronization problems. It turned out that a slot was defined as a member of the QThread subclass itself. When this slots is being called from within the main event loop, the code in the slot is being run inside the main thread.
One of the correct ways to solve this is to subclass a QObject, put all the code you want to run in the thread (including signals and slots) inside that QObject subclass.
In the main thread (in your main dialog or window for example) create an object based on this QObject subclass.
Create also a QThread object (don't subclass it).
Connect all your signals and slots.
Move the QObject based object to the QThread object and start the thread.
Example: http://www.kdedevelopers.org/node/4377
Well, this comment is just because I think that part 4 of the QThread tutorial will (involuntary) want people to add a slot like you've added the signal. 90% of the time it'll work and no problems will be seen. But afterwards that's a real nightmare to debug.
Bookmarks