MacOSX: problem with stucked mouse with modal forms

zeljko

hm...seem that it's something with QPushButton::default() or QPushButton::autoDefault().
Forms which does not have QPushButton::default() setted up does not have such problem (no default button on form).

SGaist

Sorry, for the late reply

Can you post a minimal code sample to reproduce this ? Just to ensure the same setup is used

zeljko

Here is example of problem (always reproducible)
http://holobit.homelinux.com:38180/downloads/modalWindowsQtCocoaBug.tar.gz

Howto reproduce (best way): start modalWins.app (open modalWins.app or by dbl click in Finder).
Click "Create modal form" button, then click "New dialog", in New dialog form click "New Dialog" , so you have at least 2 dialogs + modal form opened.
Click OK to close dialog. Click OK again to close second dialog.
Now try to click anything in modal form ? Can you ? I guess not.
Ok, now press ESC, so modal form is closed and only QMainWindow is opened. Can you click any button ? No.

zeljko

Here is example of problem (always reproducible)
http://holobit.homelinux.com:38180/downloads/modalWindowsQtCocoaBug.tar.gz

Howto reproduce (best way): start modalWins.app (open modalWins.app or by dbl click in Finder).
Click "Create modal form" button, then click "New dialog", in New dialog form click "New Dialog" , so you have at least 2 dialogs + modal form opened.
Click OK to close dialog. Click OK again to close second dialog.
Now try to click anything in modal form ? Can you ? I guess not.
Ok, now press ESC, so modal form is closed and only QMainWindow is opened. Can you click any button ? No.

zeljko

Another note: when you extract tar.gz inside buildXXXX directory is already compiled modalWins.app, so you don't need to install build tools on mac.
Tested on Mavericks 9.5 (intel mac 64bit).

zeljko

Another note: when you extract tar.gz inside buildXXXX directory is already compiled modalWins.app, so you don't need to install build tools on mac.
Tested on Mavericks 9.5 (intel mac 64bit).

SGaist

The application itself is not deployed so it won't run.

Anyway, it's reproducible on 10.8.

You should check the "bug report system":http://bugreports.qt.io to see if you find something similar

SGaist

The application itself is not deployed so it won't run.

Anyway, it's reproducible on 10.8.

You should check the "bug report system":http://bugreports.qt.io to see if you find something similar

zeljko

Yes, something similar is here https://bugreports.qt.io/browse/QTBUG-40585 (I've attached this example here), but there's more similar bugs (3-4 at least) about modal windows on MacOSX.
I hope that someone will fix it before 4.8.7 is out. This really makes Qt 4.8.6 unuseable under mac cocoa.

zeljko

Yes, something similar is here https://bugreports.qt.io/browse/QTBUG-40585 (I've attached this example here), but there's more similar bugs (3-4 at least) about modal windows on MacOSX.
I hope that someone will fix it before 4.8.7 is out. This really makes Qt 4.8.6 unuseable under mac cocoa.

zeljko

I've attached patch to QTBUG-40585 which fixes problem for me.

zeljko

I've attached patch to QTBUG-40585 which fixes problem for me.

SGaist

You should submit your patch through gerrit and make it reviewed for inclusion in Qt

SGaist

You should submit your patch through gerrit and make it reviewed for inclusion in Qt

zeljko

I know, but first I must make heavy tests for my patch.Already found one more bug, but that bug exists without my patch too ... yes also about modal windows. Now modal windows works, but cannot when I try to close modal window via close button in title bar it does not work.

zeljko

I know, but first I must make heavy tests for my patch.Already found one more bug, but that bug exists without my patch too ... yes also about modal windows. Now modal windows works, but cannot when I try to close modal window via close button in title bar it does not work.

SGaist

Even if its not 100% working you can submit to review, that will give you the help of other reviewers to pin-point the problem you are encountering. If you see that you have several unrelated bugs then do a submission for each separately.

SGaist

Even if its not 100% working you can submit to review, that will give you the help of other reviewers to pin-point the problem you are encountering. If you see that you have several unrelated bugs then do a submission for each separately.