Quote Originally Posted by d_stranz View Post
I believe that the move, frame, and repaint functionality is actually being provided by the window system (i.e. Windows), not Qt, but I could be wrong about that. It sounds to me as though your Qt event loop isn't being set up correctly or that the Qt events are being intercepted by the driver app before they can get to your dialog.

You can probably check for an active event loop by implementing some kind of animation in your dialog (like a progress bar or a QTimer that changes something on timeout, for example) and seeing if it updates.
This all worked without issue in Qt 4.8.4. I am putting this out there in hopes that there are different considerations for what I am doing in Qt 5 as far as the GUI module is concerned.