forked from qt-creator/qt-creator
Core: Give a hint why saving of settings are requested
Not all requests are the same, handling code might want to act differently on different request reasons. Main driver here is the handling of the debugger/analyzer main window state savings which depends on actual visibility of certain windows. Change-Id: I87b2a9149e3d09d27bc14b44aace9f2e0686db04 Reviewed-by: Eike Ziller <eike.ziller@qt.io>
This commit is contained in:
@@ -141,14 +141,21 @@ public:
|
||||
static QString systemInformation();
|
||||
static void setupScreenShooter(const QString &name, QWidget *w, const QRect &rc = QRect());
|
||||
|
||||
enum SaveSettingsReason {
|
||||
InitializationDone,
|
||||
SettingsDialogDone,
|
||||
ModeChanged,
|
||||
MainWindowClosing,
|
||||
};
|
||||
|
||||
public slots:
|
||||
static void saveSettings();
|
||||
static void saveSettings(SaveSettingsReason reason);
|
||||
|
||||
signals:
|
||||
void coreAboutToOpen();
|
||||
void coreOpened();
|
||||
void newItemDialogStateChanged();
|
||||
void saveSettingsRequested();
|
||||
void saveSettingsRequested(SaveSettingsReason reason);
|
||||
void coreAboutToClose();
|
||||
void contextAboutToChange(const QList<Core::IContext *> &context);
|
||||
void contextChanged(const Core::Context &context);
|
||||
|
||||
Reference in New Issue
Block a user