Bugzilla – Bug 1410
Mac: Can't open a modeless dialogue from a modal one.
Last modified: 2019-05-28 12:51:04 UTC
With the switch to wx3, we can't open a modeless dialogue from a modal one on Mac because the modeless dialogue does not accept mouse clicks. This has meant e.g. we can't, as we would prefer, open a modeless Help dialogue from Timer Record (bug 1407) or from the "Error importing" dialogue.
As titled, this bug can't be fixed unless wxWidgets is fixed. Do you instead expect some code-arounds as for but 1407 to fix this specific occasion of the problem?
I need more exact steps to reproduce. I get an error dialog with no ? button.
I do get such a dialog if I do File, Import... not Open as the steps say. In 2.1.3 the ? now brings up a modal help dialog, because of my recent fixes. In fact the comments and variable names in the code suggest that it was the original intention that this error dialog be modal, and the mistake was that it was not so in 2.1.2.
I just confirmed that on 2.1.1, this error dialog is modal and does not "ding." I repeat, in this instance, it was not the intention to open a modeless dialog during a modal dialog. And now the problem that was new in 2.1.2 is fixed in 2.1.3.
Paul, I get the "?" button with Open or Import if I import a text file rather than an app, but I changed the steps to Import. My intention is merely to log the bug so as to populate dependencies for bug 1405. I could (and almost did) call this an Enh. I did not realise the help dialogue for error importing was actually modal in 2.1.1 but I don't think it changes anything. Without this bug, we would still today have modeless "Help on the Internet" presumably because someone wanted that. It looks like we need a policy on whether Help dialogues are modeless or not, and whether it should be different between opening from a menu or a dialogue and different according to the help contents. Unless the policy is never to have a modeless help dialogue open from a modal one, I would argue that this bug (or enh) stands.
Testing on macOS 10.1.45 with 2.3.2 This works fine now - I get linked at Step 3 to the proper help page in the Manual "Importing Audio"