MessageDialog does not work on iOS

[anda_skoa]

The bug report might not be applicable, I think the problem there was showing the message dialog "too soon", i.e. while the application was not fully ready yet.
My guess is your dialog is triggered via user interaction.

Have you tried a very minimal example, just some UI for the user to trigger the message dialog?

Cheers,
_

P.S.: don't concatenate runtime data into a translated string, positioning will depend on the translation. Use the arg() mechansim instead

[Urthas]

Have you tried a very minimal example, just some UI for the user to trigger the message dialog?

In fact, my "application" at this point is all UI, and quite minimal: a Page containing a dummy ListModel gets pushed onto a StackView; each delegate has a "Delete" Button whose onClicked handler calls the alertDeletion() function shown. There is as yet not a single line of C++ code beyond the boilerplate in main.cpp.

Thanks for the tip re: qsTr().

Since posting I've tried running on a different physical device but the result was the same. I'm going to confirm that there isn't something silly happening with the MessageDialog such as a width or height of zero. Once the sanity checks are concluded, I will try exposing a subclass of QMessageBox to QML, per the supposed fallback mechanism in the documentation.

Any further insight is appreciated.

[Urthas]

Findings re: width and height as shown by console.debug() statements in my custom MessageDialog:

qml: Component.onCompleted() - visible:false
/* button press event */
qml: DeleteDLCDialog::onVisibleChanged() - visible:true
qml: 	    height:0
qml: 	    width:0

qml: Component.onCompleted() - visible:false
/* button press event */
qml: DeleteDLCDialog::onVisibleChanged() - visible:true
qml: 	    height:0
qml: 	    width:0

To copy to clipboard, switch view to plain text mode 

What's even more disturbing is that if I explicitly set the width and height, the correct values are printed but there is still no dialog in evidence!

[Urthas]

It turns out that this is partially a result of how the iOS plugin works, and partially a bug related to the supposed fallback mechanism. See the bug report here (fixed for 5.7.1). Setting the modality to Qt.ApplicationModal does the trick.