QPushButton gets stuck drawing pressed when transfer of focus to button interrupted

[high_flyer]

If the user types in the control and then clicks the button the messagebox pops but the button gets stuck being drawn looking like it’s pressed. How can I make that stop?

The reason for this is that you are calling you message box in a modal state with exec().
This causes the applications even loop to wait for the message box to be dismissed, and therfore, the paintEvent for the pushbuttons is not being handled until the message box is not dismissed.
What you can do is:
1. Rethink your design. If the user is shifting input focus from a control, when the application logic states that this should not be allowed, its better to force the focus to stay on the focused control than to send a message box.
You could in addition to forcing the focus, have somewhere a message saying why it is being done, similar to what many applications do in the status bar.
2. Show the message box with show() and not exec(), but then it wont be modal, can be covered by other windows, and can bring to that that it will be immediately covered by another window so that the user not even notice it was popped.

[bob_smith]

Got it answered here without having to resort to either option (unless something comes up in the future but seems to work so far): http://stackoverflow.com/questions/4...tton-is-interr

[high_flyer]

if it works for you - Great!

[bob_smith]

Well we haven’t made all the dialogs yet nor run through all the testing so something could come up. I’m still fairly new to Qt but the only potential problem I see is something getting between the creation of a user QEvent in test_line_edit::focusOutEvent and it getting processed in test_line_edit::customEvent. Do you know if that’s possible? Seems like it might be but I don’t really know under what conditions… Also are there any other obvious problems with this approach that I might be missing?

[high_flyer]

Well, again, you can bend anything and force anything.
But I still think that the problem is a design problem, not an implementation problem.
You can work around design problem by forcing stuff, but then you are on slippery road of surprises.