[digikam] [Bug 388610] digikam doesn't use native or KDE file dialogs

2018-01-06 Thread RJVB
https://bugs.kde.org/show_bug.cgi?id=388610 --- Comment #6 from RJVB --- That *is* a bit like dumping all SIMD and other optimisations and just use good old software of all algorithms because that's so much easier to maintain (and the result will perform and look similarly

[digikam] [Bug 388610] digikam doesn't use native or KDE file dialogs

2018-01-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=388610 --- Comment #5 from caulier.gil...@gmail.com --- BTW, are you talking about desktops that use the gtk3 QPA? You can detect the name of the platform being used at runtime and use that to decide what the default should be, too. ==> definitively no. It's

[digikam] [Bug 388610] digikam doesn't use native or KDE file dialogs

2018-01-06 Thread RJVB
https://bugs.kde.org/show_bug.cgi?id=388610 --- Comment #4 from RJVB --- I don't really see how that excludes the possibility to bring the default under control of a build option. That option could be off by default itself, or do some fancy kind of detection if the user

[digikam] [Bug 388610] digikam doesn't use native or KDE file dialogs

2018-01-06 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=388610 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com

[digikam] [Bug 388610] digikam doesn't use native or KDE file dialogs

2018-01-06 Thread RJVB
https://bugs.kde.org/show_bug.cgi?id=388610 --- Comment #2 from RJVB --- Dang, another case where searching with the appropriate terms didn't take me to the existing bug report! I found the commit and it applies to the 5.7.0 source. The only thing one could still want is a

[digikam] [Bug 388610] digikam doesn't use native or KDE file dialogs

2018-01-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=388610 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||5.8.0 Resolution|---