KMediaWindow inherits KXmlGuiWindow which inherits KMainWindow, which
inherits QMainWindow, which has a menuBar() getter that should not be
confused with the KMediaWindow class slot. same goes for
KMediaWindow::menubar() (now named KMediaWindow::slotMenubar()) and
QMainWindow::menuBar()
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
now that phase 2 is properly done (see
86082941ab933b36fb7df267f3abd2625757f4ba in kdelibs repo) it could
block for a few seconds
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
should the worst happen and kded4 crash the share settings will be saved
regardless (unless it crashes because of KDirShareModule::share())
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
if Xrender is not found a fatal message will be issued by the top-level
CMakeLists file because it is required by KWin compositor for example
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
the style KCM for example emits changes via
KGlobalSettings::self()->emitChange() however it does not wait for the
KGlobalSettings::settingsChanged() signal (which means settings are
reloaded) before running krdb, font and palette settings are likely subject
to this race-condition but for now that will do
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
note that the only way to set EffectsEnabled, EffectFadeMenu,
EffectFadeTooltip and EffectAnimateCombo was manually (by editing the
~/.katana/share/config/kdeglobals config file) because there is no GUI for
those config options but there is for the graphics effects level
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
note that the KMessageWidget animation is a fade effect so
KateFadeEffect was doing what KMessageWidget already has the feature
for, grow/shrink effect is not a thing
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
for some reason KSMShutdownFeedback::stop() was not doing anything when the
KWin effect was taking care of the logout effect but KWin also does not
apply the effect to windows other than the one created by ksmserver
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
the effect is very much bound to the window manager (KWin) because if
applications require attention (such as confirmation to cancel any
pending changes) their window or any dialog they pop may have to be
raised, will have to be focused and not be grayed out
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
effects for example may have their own selection (the startupfeedback
effect used to claim _KDE_STARTUP_FEEDBACK for example) so if other
window manager wants to claim selection/atom owned by KWin effect effects
have to be deinitialized before disowning the window manager selection
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
the window manager itself may want to do something session management
related (KWin does) and as such ksmserver has to be in operational state
before the window manager is killed
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
