Binary Elysium

Hey there! My name is Casey. I'm a software developer, nomad, language lover, and coffee fiend.

The Lessons of a Master

24 January 2009

Several of us at Camp KDE—myself included—owe a great debt to Till Adam. When he came to the sunny, beautiful beaches of Jamaica, instead of spending his days lounging on the shore or swimming in the warm Caribbean, he chose to pen himself in a stuffy room with a dozen geeks and teach them Qt.

Till works for Klarälvdalens Datakonsult AB (KDAB), the Qt consultancy firm. Besides working on large-scale, enterprise Qt applications, KDAB provides professional Qt training to such companies as IBM, Boeing, Ericsson, and J.D. Edwards. These training sessions usually run a few thousand Euros per person. With the OK from Nokia and Qt Software, Till provided us with a mini two day training course for free!

While the content and materials Till used during the sessions is copyrighted, the information I learned is not. With his permission I’m going to discuss a few pointers in this post. The topics covered somewhat basic/intermediate Qt skills, so those of you who have been programming with Qt for any length of time might not find anything new or interesting. However, for those, like me, who haven’t quite developed our Qt Fu to the Master level, take away tips from here knowing it was passed from a master.

#1 Most Common Performance Issue in Qt Converting from a QPixmap to QImage too often.

This tip is actually fairly well known, but apparently KDAB consultants run across this mistake very often while in the field. There is a great discussion of this topic over at KDE’s techbase. In summary:

  • A QImage is stored in main memory
  • A QPixmap is stored in video memory
  • Converting from a QPixmap to a QImage is a very expensive operation (see the above article for the explanation)

#1 Most Common Cause of Crashes in Qt Deleting this from slots

This tip needs some more explanation. Essentially, a mistake many Qt programmers do is include executable code after emitting a signal. Consider this flow of execution:

  • The function Produce::blend() emits signal pineapple()
  • The slot slotBlender() deletes the instance of Produce
  • The signal/slot connection returns to the function Produce::blend(), which has some other executable code such as variable assignments after the emit.
  • Crash. Since the slot deleted Produce, any code following the emit statement that modifies memory is now attempting to write to invalid memory.
  • One good practice to follow is: don’t have any executable code following the last emit statement in your objects' methods. However, the real solution is: Use deleteLater() on your QObjects.

    This post is getting somewhat lengthy and I potentially still have two topics to cover (Threading and Model/View). Most likely I’ll dedicate a post regarding threading in Qt (I took better notes during that talk) in the next couple days. Many thanks to Till for the sessions, as well as KDAB and Qt Software for allowing them to happen.

Recent Posts

← More Awesome Stuff · page layout by Sean Palmer
·header image by cloaks