| Summary: | [Testcase] Native KFileDialog on Windows does not show custom widget | ||
|---|---|---|---|
| Product: | [Unmaintained] kfile | Reporter: | Thomas Friedrichsmeier <thomas.friedrichsmeier> |
| Component: | general | Assignee: | KDE-Windows <kde-windows> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | normal | CC: | nate |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
Is this still an issue with KDE Frameworks 5.44 or greater? Not sure if this is relevant enough to still fix it, considering KFileDialog is only in kdelibs4support, and not too many applications seem to have suffered from it, so far. However, it is definitely still present. Just look at the latest revision of kfiledialog.cpp (as of today: https://cgit.kde.org/kdelibs4support.git/tree/src/kio/kfiledialog.cpp?id=1ba106517481213f116bfa5115dfe4d053176c17), between lines 250 and 260, if the dialog is native, the "customWidget" parameter is clearly never used. Changing status back to confirmed. I'm afraid we won't be able to address this, as the KDE4 stuff has been unsupported for several years. |
Version: (using KDE 4.4.1) OS: MS Windows Installed from: MS Windows Native KFileDialogs on Windows do not show any custom widget (4th argument to the KFileDialog-constructor). I.e. no label is shown for a KFileDialog constructed like this: new KFileDialog (KUrl (), QString (), 0, new QLabel ("It's just a label...")); For non-native dialogs, the label is shown correctly. Testcase: See attachment #42205 [details] on bug #231913 . 1) In System settings->Advanced->Platform check "Use native system file dialogs". 2) In the testcase application, click the second button from the top. Dialog shows without label. 3) Uncheck "Use native system file dialogs" and restart the testcase application. 4) Click the second button again. Dialog shows with label as expected. Note: The third button claims to feature a custom widget as well, but doesn't. Sorry. Only the second button of the testcase application is relevant for this report.