macOS wxFileDlg wxFD_SAVE Crashes (Issue #26129)
bartvanstiphout
bartvanstiphout created an issue (wxWidgets/wxWidgets#26129)Bug description:
Using the wxFileDlg on macOS with the style wxFD_SAVE will cause a fatal assertion.
Expected vs observed behaviour:
Expect: Open a file save dialog
Observed: Assert
Snippet from the docs that causes the crash on macOS
wxFileDialog
saveFileDialog(this, _("Save XYZ file"), "", "",
"XYZ files (*.xyz)|*.xyz", wxFD_SAVE|wxFD_OVERWRITE_PROMPT);
if (saveFileDialog.ShowModal() == wxID_CANCEL)
return; // the user changed idea...
To Reproduce:
Use the above snippet and running the application will cause a fatal assertion.
Platform and version information
- wxWidgets version 3.2.9
- wxWidgets wxOSX
- macOS 15.7 / Xcode
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
VZ
vadz left a comment (wxWidgets/wxWidgets#26129)What does the assert say?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
bartvanstiphout
bartvanstiphout left a comment (wxWidgets/wxWidgets#26129)—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
VZ
vadz left a comment (wxWidgets/wxWidgets#26129)I can't reproduce this with the following diff in master:
diff --git a/samples/dialogs/dialogs.cpp b/samples/dialogs/dialogs.cpp index def41615c0..8982250985 100644 --- a/samples/dialogs/dialogs.cpp +++ b/samples/dialogs/dialogs.cpp @@ -2037,10 +2037,10 @@ void MyFrame::FileSave(wxCommandEvent& WXUNUSED(event) ) "Testing save file dialog", wxEmptyString, "myletter.doc", - "Text files (*.txt)|*.txt|Document files (*.doc;*.ods)|*.doc;*.ods", + "FIXME files (*.xyz)|*.xyz", wxFD_SAVE|wxFD_OVERWRITE_PROMPT); - dialog.SetFilterIndex(1); + // FIXME dialog.SetFilterIndex(1); // This tests the (even more simplified) example from the docs. class EncryptHook : public wxFileDialogCustomizeHook
which is weird because I don't see any changes there compared to 3.2.
Can you see the problem in the sample with the patch above? If no, please make a minimal patch allowing to reproduce it there. TIA!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.