Well, I admit that the comment looks peculiar at first sight, but it really makes sense because QObject::startTimer() is rarely used directly, but mostly via QTimer. Besides, this way the warning is fully understandable to both QObject::startTimer() and QTimer users, isn't it?






Reply With Quote
Bookmarks