Thanks!

So, Ctrl+Q always quits without confirmation? What about having a

singal aboutToQuit(var event)

and then do:

onActivated: {
    var event = {accepted: false}
    aboutToQuit(event);
    if (!event.accepted) {
        Qt.quit();
    }
}

Then an app can

onAboutToQuit: {
    if (hasUnsavedChanges) {
        event.accepted = true;
        // ask for confirmation
    }
}

In D2790#51966, @broulik wrote:

So, Ctrl+Q always quits without confirmation? What about having a

singal aboutToQuit(var event)

and then do:

onActivated: {
    var event = {accepted: false}
    aboutToQuit(event);
    if (!event.accepted) {
        Qt.quit();
    }
}

Then an app can

onAboutToQuit: {
    if (hasUnsavedChanges) {
        event.accepted = true;
        // ask for confirmation
    }
}

That could be interesting but could be out of scope for the patch? There's other ways the application can be closed.

I would like it done as Kai's suggestion, I would call the signal quitRequested?
about the other ways to quit, i guess it's window closing, which i don't think we can intercept in any way?

You can: http://doc.qt.io/qt-5/qml-qtquick-window-window.html#closing-signal

hmm, can it be intercepted since Applicationwindow can't be subclassed from c++? i can think about an ugly event filter, but ouch..