Review Request 127827: open/fetch project: restore broken workflows after native file dialog port

[René J.V. Bertin]

On Tuesday May 17 2016 20:31:58 Sven Brauch wrote:

Hi,

Tangentially related:

> >     Maybe Aleix meant non-native = not pure QFileDialog, referring to the fact that under X11 (and Wayland?) KDevelop uses KDE file dialogs rather than QFileDialogs?
> > 
> > Sven Brauch wrote:
> >     No, instantiating QFileDialog under Plasma uses the KDE file dialog because of the platform plugin which is being loaded. 

My Mac KDE platform theme plugin shouldn't do that:

QPlatformDialogHelper *KdeMacTheme::createPlatformDialogHelper(QPlatformTheme::DialogType type) const
{
    // always prefer native dialogs
    if (nativeTheme) {
        return nativeTheme->createPlatformDialogHelper(type);
    }
    QPlatformDialogHelper *helper = KdePlatformTheme::createPlatformDialogHelper(type);
// etc
}

This leads (?) to a bit annoying behaviour. When I invoke "Save As" a native dialog opens, and when I pick an existing file I get a native "are you sure" message. When I chose "replace" because that's what I want, I get a second, KF5-based "are you sure" dialog. Apparently that one is posted by KTextEdit.

Any ideas if there's a robust way to avoid that, i.e. one that doesn't lead to failing to warn the user?

R.