//Auto-generated by kalyptus. DO NOT EDIT. package org.kde.koala; import org.kde.qt.TQMetaObject; import org.kde.qt.QtSupport; import org.kde.qt.TQObject; import org.kde.qt.TQPixmap; import org.kde.qt.TQSessionManager; import java.util.ArrayList; import org.kde.qt.TQEvent; import org.kde.qt.TQWidget; import org.kde.qt.TQPalette; public interface TDEApplicationSignals { /** Emitted when TDEApplication has changed its palette due to a KControl request. Normally, widgets will update their palette automatically, but you should connect to this to program special behavior. @short Emitted when TDEApplication has changed its palette due to a KControl request. */ void tdedisplayPaletteChanged(); /** Emitted when TDEApplication has changed its GUI style in response to a KControl request. Normally, widgets will update their styles automatically (as they would respond to an explicit setGUIStyle() call), but you should connect to this to program special behavior. @short Emitted when TDEApplication has changed its GUI style in response to a KControl request. */ void tdedisplayStyleChanged(); /** Emitted when TDEApplication has changed its font in response to a KControl request. Normally widgets will update their fonts automatically, but you should connect to this to monitor global font changes, especially if you are using explicit fonts. Note: If you derive from a TQWidget-based class, a faster method is to reimplement TQWidget.fontChange(). This is the preferred way to get informed about font updates. @short Emitted when TDEApplication has changed its font in response to a KControl request. */ void tdedisplayFontChanged(); /** Emitted when TDEApplication has changed either its GUI style, its font or its palette in response to a tdedisplay request. Normally, widgets will update their styles automatically, but you should connect to this to program special behavior. @short Emitted when TDEApplication has changed either its GUI style, its font or its palette in response to a tdedisplay request. */ void appearanceChanged(); /** Emitted when the settings for toolbars have been changed. TDEToolBar will know what to do. @short Emitted when the settings for toolbars have been changed. */ void toolbarAppearanceChanged(int arg1); /** Emitted when the desktop background has been changed by kcmdisplay. @param desk The desktop whose background has changed. @short Emitted when the desktop background has been changed by kcmdisplay. */ void backgroundChanged(int desk); /** Emitted when the global settings have been changed - see TDEGlobalSettings TDEApplication takes care of calling reparseConfiguration on TDEGlobal.config() so that applications/classes using this only have to re-read the configuration @param category the category among the enum above @short Emitted when the global settings have been changed - see TDEGlobalSettings TDEApplication takes care of calling reparseConfiguration on TDEGlobal.config() so that applications/classes using this only have to re-read the configuration */ void settingsChanged(int category); /** Emitted when the global icon settings have been changed. @param group the new group @short Emitted when the global icon settings have been changed. */ void iconChanged(int group); /** Emitted when a KIPC user message has been received. @param id the message id @param data the data @short Emitted when a KIPC user message has been received. @see KIPC @see KIPC#Message @see #addKipcEventMask @see #removeKipcEventMask */ void kipcMessage(int id, int data); /** Session management asks you to save the state of your application. This signal is provided for compatibility only. For new applications, simply use TDEMainWindow. By reimplementing TDEMainWindow.queryClose(), TDEMainWindow.saveProperties() and TDEMainWindow.readProperties() you can simply handle session management for applications with multiple toplevel windows. For purposes without TDEMainWindow, create an instance of KSessionManaged and reimplement the functions KSessionManaged.commitData() and/or KSessionManaged.saveState() If you still want to use this signal, here is what you should do: Connect to this signal in order to save your data. Do NOT manipulate the UI in that slot, it is blocked by the session manager. Use the sessionConfig() TDEConfig object to store all your instance specific data. Do not do any closing at this point! The user may still select Cancel wanting to continue working with your application. Cleanups could be done after shutDown() (see the following). @short Session management asks you to save the state of your application. */ void saveYourself(); /** Your application is killed. Either by your program itself, xkill or (the usual case) by KDE's logout. The signal is particularly useful if your application has to do some last-second cleanups. Note that no user interaction is possible at this state. @short Your application is killed. */ void shutDown(); }