2020-08-02 22:22:19 +00:00
|
|
|
/*
|
|
|
|
KWin - the KDE window manager
|
|
|
|
This file is part of the KDE project.
|
2008-01-24 10:36:32 +00:00
|
|
|
|
2020-08-02 22:22:19 +00:00
|
|
|
SPDX-FileCopyrightText: 2008, 2009 Martin Gräßlin <mgraesslin@kde.org>
|
2008-01-24 10:36:32 +00:00
|
|
|
|
2020-08-02 22:22:19 +00:00
|
|
|
SPDX-License-Identifier: GPL-2.0-or-later
|
|
|
|
*/
|
2008-01-24 10:36:32 +00:00
|
|
|
|
|
|
|
#ifndef KWIN_FLIPSWITCH_H
|
|
|
|
#define KWIN_FLIPSWITCH_H
|
|
|
|
|
|
|
|
#include <kwineffects.h>
|
2015-02-01 03:29:50 +00:00
|
|
|
#include <QMatrix4x4>
|
2009-07-21 10:18:48 +00:00
|
|
|
#include <QQueue>
|
2011-03-14 21:50:05 +00:00
|
|
|
#include <QTimeLine>
|
2017-11-08 10:23:00 +00:00
|
|
|
#include <QFont>
|
2009-07-21 10:18:48 +00:00
|
|
|
|
2008-01-24 10:36:32 +00:00
|
|
|
namespace KWin
|
|
|
|
{
|
|
|
|
|
|
|
|
class FlipSwitchEffect
|
2011-02-25 19:25:21 +00:00
|
|
|
: public Effect
|
2011-01-30 14:34:42 +00:00
|
|
|
{
|
2009-07-21 10:18:48 +00:00
|
|
|
Q_OBJECT
|
2012-08-11 09:24:37 +00:00
|
|
|
Q_PROPERTY(bool tabBox READ isTabBox)
|
|
|
|
Q_PROPERTY(bool tabBoxAlternative READ isTabBoxAlternative)
|
|
|
|
Q_PROPERTY(int duration READ duration)
|
|
|
|
Q_PROPERTY(int angle READ angle)
|
|
|
|
Q_PROPERTY(qreal xPosition READ xPosition)
|
|
|
|
Q_PROPERTY(qreal yPosition READ yPosition)
|
|
|
|
Q_PROPERTY(bool windowTitle READ isWindowTitle)
|
2011-01-30 14:34:42 +00:00
|
|
|
public:
|
|
|
|
FlipSwitchEffect();
|
Run clang-tidy with modernize-use-override check
Summary:
Currently code base of kwin can be viewed as two pieces. One is very
ancient, and the other one is more modern, which uses new C++ features.
The main problem with the ancient code is that it was written before
C++11 era. So, no override or final keywords, lambdas, etc.
Quite recently, KDE compiler settings were changed to show a warning if
a virtual method has missing override keyword. As you might have already
guessed, this fired back at us because of that ancient code. We had
about 500 new compiler warnings.
A "solution" was proposed to that problem - disable -Wno-suggest-override
and the other similar warning for clang. It's hard to call a solution
because those warnings are disabled not only for the old code, but also
for new. This is not what we want!
The main argument for not actually fixing the problem was that git
history will be screwed as well because of human factor. While good git
history is a very important thing, we should not go crazy about it and
block every change that somehow alters git history. git blame allows to
specify starting revision for a reason.
The other argument (human factor) can be easily solved by using tools
such as clang-tidy. clang-tidy is a clang-based linter for C++. It can
be used for various things, e.g. fixing coding style(e.g. add missing
braces to if statements, readability-braces-around-statements check),
or in our case add missing override keywords.
Test Plan: Compiles.
Reviewers: #kwin, davidedmundson
Reviewed By: #kwin, davidedmundson
Subscribers: davidedmundson, apol, romangg, kwin
Tags: #kwin
Differential Revision: https://phabricator.kde.org/D22371
2019-07-22 16:52:26 +00:00
|
|
|
~FlipSwitchEffect() override;
|
2008-01-24 10:36:32 +00:00
|
|
|
|
Run clang-tidy with modernize-use-override check
Summary:
Currently code base of kwin can be viewed as two pieces. One is very
ancient, and the other one is more modern, which uses new C++ features.
The main problem with the ancient code is that it was written before
C++11 era. So, no override or final keywords, lambdas, etc.
Quite recently, KDE compiler settings were changed to show a warning if
a virtual method has missing override keyword. As you might have already
guessed, this fired back at us because of that ancient code. We had
about 500 new compiler warnings.
A "solution" was proposed to that problem - disable -Wno-suggest-override
and the other similar warning for clang. It's hard to call a solution
because those warnings are disabled not only for the old code, but also
for new. This is not what we want!
The main argument for not actually fixing the problem was that git
history will be screwed as well because of human factor. While good git
history is a very important thing, we should not go crazy about it and
block every change that somehow alters git history. git blame allows to
specify starting revision for a reason.
The other argument (human factor) can be easily solved by using tools
such as clang-tidy. clang-tidy is a clang-based linter for C++. It can
be used for various things, e.g. fixing coding style(e.g. add missing
braces to if statements, readability-braces-around-statements check),
or in our case add missing override keywords.
Test Plan: Compiles.
Reviewers: #kwin, davidedmundson
Reviewed By: #kwin, davidedmundson
Subscribers: davidedmundson, apol, romangg, kwin
Tags: #kwin
Differential Revision: https://phabricator.kde.org/D22371
2019-07-22 16:52:26 +00:00
|
|
|
void reconfigure(ReconfigureFlags) override;
|
Provide expected presentation time to effects
Effects are given the interval between two consecutive frames. The main
flaw of this approach is that if the Compositor transitions from the idle
state to "active" state, i.e. when there is something to repaint,
effects may see a very large interval between the last painted frame and
the current. In order to address this issue, the Scene invalidates the
timer that is used to measure time between consecutive frames before the
Compositor is about to become idle.
While this works perfectly fine with Xinerama-style rendering, with per
screen rendering, determining whether the compositor is about to idle is
rather a tedious task mostly because a single output can't be used for
the test.
Furthermore, since the Compositor schedules pointless repaints just to
ensure that it's idle, it might take several attempts to figure out
whether the scene timer must be invalidated if you use (true) per screen
rendering.
Ideally, all effects should use a timeline helper that is aware of the
underlying render loop and its timings. However, this option is off the
table because it will involve a lot of work to implement it.
Alternative and much simpler option is to pass the expected presentation
time to effects rather than time between consecutive frames. This means
that effects are responsible for determining how much animation timelines
have to be advanced. Typically, an effect would have to store the
presentation timestamp provided in either prePaint{Screen,Window} and
use it in the subsequent prePaint{Screen,Window} call to estimate the
amount of time passed between the next and the last frames.
Unfortunately, this is an API incompatible change. However, it shouldn't
take a lot of work to port third-party binary effects, which don't use the
AnimationEffect class, to the new API. On the bright side, we no longer
need to be concerned about the Compositor getting idle.
We do still try to determine whether the Compositor is about to idle,
primarily, because the OpenGL render backend swaps buffers on present,
but that will change with the ongoing compositing timing rework.
2020-11-20 15:44:04 +00:00
|
|
|
void prePaintScreen(ScreenPrePaintData& data, std::chrono::milliseconds presentTime) override;
|
2019-10-29 22:04:15 +00:00
|
|
|
void paintScreen(int mask, const QRegion ®ion, ScreenPaintData& data) override;
|
Run clang-tidy with modernize-use-override check
Summary:
Currently code base of kwin can be viewed as two pieces. One is very
ancient, and the other one is more modern, which uses new C++ features.
The main problem with the ancient code is that it was written before
C++11 era. So, no override or final keywords, lambdas, etc.
Quite recently, KDE compiler settings were changed to show a warning if
a virtual method has missing override keyword. As you might have already
guessed, this fired back at us because of that ancient code. We had
about 500 new compiler warnings.
A "solution" was proposed to that problem - disable -Wno-suggest-override
and the other similar warning for clang. It's hard to call a solution
because those warnings are disabled not only for the old code, but also
for new. This is not what we want!
The main argument for not actually fixing the problem was that git
history will be screwed as well because of human factor. While good git
history is a very important thing, we should not go crazy about it and
block every change that somehow alters git history. git blame allows to
specify starting revision for a reason.
The other argument (human factor) can be easily solved by using tools
such as clang-tidy. clang-tidy is a clang-based linter for C++. It can
be used for various things, e.g. fixing coding style(e.g. add missing
braces to if statements, readability-braces-around-statements check),
or in our case add missing override keywords.
Test Plan: Compiles.
Reviewers: #kwin, davidedmundson
Reviewed By: #kwin, davidedmundson
Subscribers: davidedmundson, apol, romangg, kwin
Tags: #kwin
Differential Revision: https://phabricator.kde.org/D22371
2019-07-22 16:52:26 +00:00
|
|
|
void postPaintScreen() override;
|
Provide expected presentation time to effects
Effects are given the interval between two consecutive frames. The main
flaw of this approach is that if the Compositor transitions from the idle
state to "active" state, i.e. when there is something to repaint,
effects may see a very large interval between the last painted frame and
the current. In order to address this issue, the Scene invalidates the
timer that is used to measure time between consecutive frames before the
Compositor is about to become idle.
While this works perfectly fine with Xinerama-style rendering, with per
screen rendering, determining whether the compositor is about to idle is
rather a tedious task mostly because a single output can't be used for
the test.
Furthermore, since the Compositor schedules pointless repaints just to
ensure that it's idle, it might take several attempts to figure out
whether the scene timer must be invalidated if you use (true) per screen
rendering.
Ideally, all effects should use a timeline helper that is aware of the
underlying render loop and its timings. However, this option is off the
table because it will involve a lot of work to implement it.
Alternative and much simpler option is to pass the expected presentation
time to effects rather than time between consecutive frames. This means
that effects are responsible for determining how much animation timelines
have to be advanced. Typically, an effect would have to store the
presentation timestamp provided in either prePaint{Screen,Window} and
use it in the subsequent prePaint{Screen,Window} call to estimate the
amount of time passed between the next and the last frames.
Unfortunately, this is an API incompatible change. However, it shouldn't
take a lot of work to port third-party binary effects, which don't use the
AnimationEffect class, to the new API. On the bright side, we no longer
need to be concerned about the Compositor getting idle.
We do still try to determine whether the Compositor is about to idle,
primarily, because the OpenGL render backend swaps buffers on present,
but that will change with the ongoing compositing timing rework.
2020-11-20 15:44:04 +00:00
|
|
|
void prePaintWindow(EffectWindow *w, WindowPrePaintData &data, std::chrono::milliseconds presentTime) override;
|
Run clang-tidy with modernize-use-override check
Summary:
Currently code base of kwin can be viewed as two pieces. One is very
ancient, and the other one is more modern, which uses new C++ features.
The main problem with the ancient code is that it was written before
C++11 era. So, no override or final keywords, lambdas, etc.
Quite recently, KDE compiler settings were changed to show a warning if
a virtual method has missing override keyword. As you might have already
guessed, this fired back at us because of that ancient code. We had
about 500 new compiler warnings.
A "solution" was proposed to that problem - disable -Wno-suggest-override
and the other similar warning for clang. It's hard to call a solution
because those warnings are disabled not only for the old code, but also
for new. This is not what we want!
The main argument for not actually fixing the problem was that git
history will be screwed as well because of human factor. While good git
history is a very important thing, we should not go crazy about it and
block every change that somehow alters git history. git blame allows to
specify starting revision for a reason.
The other argument (human factor) can be easily solved by using tools
such as clang-tidy. clang-tidy is a clang-based linter for C++. It can
be used for various things, e.g. fixing coding style(e.g. add missing
braces to if statements, readability-braces-around-statements check),
or in our case add missing override keywords.
Test Plan: Compiles.
Reviewers: #kwin, davidedmundson
Reviewed By: #kwin, davidedmundson
Subscribers: davidedmundson, apol, romangg, kwin
Tags: #kwin
Differential Revision: https://phabricator.kde.org/D22371
2019-07-22 16:52:26 +00:00
|
|
|
void paintWindow(EffectWindow* w, int mask, QRegion region, WindowPaintData& data) override;
|
|
|
|
void grabbedKeyboardEvent(QKeyEvent* e) override;
|
|
|
|
void windowInputMouseEvent(QEvent* e) override;
|
|
|
|
bool isActive() const override;
|
2008-12-04 08:47:07 +00:00
|
|
|
|
2014-03-24 10:50:09 +00:00
|
|
|
int requestedEffectChainPosition() const override {
|
|
|
|
return 50;
|
|
|
|
}
|
|
|
|
|
2011-01-30 14:34:42 +00:00
|
|
|
static bool supported();
|
2012-08-11 09:24:37 +00:00
|
|
|
|
|
|
|
// for properties
|
|
|
|
bool isTabBox() const {
|
|
|
|
return m_tabbox;
|
|
|
|
}
|
|
|
|
bool isTabBoxAlternative() const {
|
|
|
|
return m_tabboxAlternative;
|
|
|
|
}
|
|
|
|
int duration() const {
|
|
|
|
return m_timeLine.duration();
|
|
|
|
}
|
|
|
|
int angle() const {
|
|
|
|
return m_angle;
|
|
|
|
}
|
|
|
|
qreal xPosition() const {
|
|
|
|
return m_xPosition;
|
|
|
|
}
|
|
|
|
qreal yPosition() const {
|
|
|
|
return m_yPosition;
|
|
|
|
}
|
|
|
|
bool isWindowTitle() const {
|
|
|
|
return m_windowTitle;
|
|
|
|
}
|
2011-01-30 14:34:42 +00:00
|
|
|
private Q_SLOTS:
|
|
|
|
void toggleActiveCurrent();
|
|
|
|
void toggleActiveAllDesktops();
|
2020-01-14 16:42:24 +00:00
|
|
|
void globalShortcutChanged(QAction *action, const QKeySequence &shortcut);
|
2012-01-29 11:29:24 +00:00
|
|
|
void slotWindowAdded(KWin::EffectWindow* w);
|
|
|
|
void slotWindowClosed(KWin::EffectWindow *w);
|
2011-03-06 11:15:16 +00:00
|
|
|
void slotTabBoxAdded(int mode);
|
|
|
|
void slotTabBoxClosed();
|
|
|
|
void slotTabBoxUpdated();
|
2012-03-29 09:11:10 +00:00
|
|
|
void slotTabBoxKeyEvent(QKeyEvent* event);
|
2009-07-21 10:18:48 +00:00
|
|
|
|
2011-01-30 14:34:42 +00:00
|
|
|
private:
|
|
|
|
class ItemInfo;
|
|
|
|
enum SwitchingDirection {
|
|
|
|
DirectionForward,
|
|
|
|
DirectionBackward
|
|
|
|
};
|
|
|
|
enum FlipSwitchMode {
|
|
|
|
TabboxMode,
|
|
|
|
CurrentDesktopMode,
|
|
|
|
AllDesktopsMode
|
2009-07-21 10:18:48 +00:00
|
|
|
};
|
2011-01-30 14:34:42 +00:00
|
|
|
void setActive(bool activate, FlipSwitchMode mode);
|
|
|
|
bool isSelectableWindow(EffectWindow *w) const;
|
|
|
|
void scheduleAnimation(const SwitchingDirection& direction, int distance = 1);
|
|
|
|
void adjustWindowMultiScreen(const EffectWindow *w, WindowPaintData& data);
|
2012-05-25 07:04:58 +00:00
|
|
|
void selectNextOrPreviousWindow(bool forward);
|
|
|
|
inline void selectNextWindow() { selectNextOrPreviousWindow(true); }
|
|
|
|
inline void selectPreviousWindow() { selectNextOrPreviousWindow(false); }
|
2012-03-29 08:34:33 +00:00
|
|
|
/**
|
|
|
|
* Updates the caption of the caption frame.
|
|
|
|
* Taking care of rewording the desktop client.
|
2012-03-30 06:12:23 +00:00
|
|
|
* As well sets the icon for the caption frame.
|
2019-07-29 18:58:33 +00:00
|
|
|
*/
|
2012-03-29 08:34:33 +00:00
|
|
|
void updateCaption();
|
2011-01-30 14:34:42 +00:00
|
|
|
QQueue< SwitchingDirection> m_scheduledDirections;
|
|
|
|
EffectWindow* m_selectedWindow;
|
2011-03-14 21:50:05 +00:00
|
|
|
QTimeLine m_timeLine;
|
|
|
|
QTimeLine m_startStopTimeLine;
|
2020-09-09 13:03:02 +00:00
|
|
|
QEasingCurve m_currentAnimationEasingCurve;
|
Provide expected presentation time to effects
Effects are given the interval between two consecutive frames. The main
flaw of this approach is that if the Compositor transitions from the idle
state to "active" state, i.e. when there is something to repaint,
effects may see a very large interval between the last painted frame and
the current. In order to address this issue, the Scene invalidates the
timer that is used to measure time between consecutive frames before the
Compositor is about to become idle.
While this works perfectly fine with Xinerama-style rendering, with per
screen rendering, determining whether the compositor is about to idle is
rather a tedious task mostly because a single output can't be used for
the test.
Furthermore, since the Compositor schedules pointless repaints just to
ensure that it's idle, it might take several attempts to figure out
whether the scene timer must be invalidated if you use (true) per screen
rendering.
Ideally, all effects should use a timeline helper that is aware of the
underlying render loop and its timings. However, this option is off the
table because it will involve a lot of work to implement it.
Alternative and much simpler option is to pass the expected presentation
time to effects rather than time between consecutive frames. This means
that effects are responsible for determining how much animation timelines
have to be advanced. Typically, an effect would have to store the
presentation timestamp provided in either prePaint{Screen,Window} and
use it in the subsequent prePaint{Screen,Window} call to estimate the
amount of time passed between the next and the last frames.
Unfortunately, this is an API incompatible change. However, it shouldn't
take a lot of work to port third-party binary effects, which don't use the
AnimationEffect class, to the new API. On the bright side, we no longer
need to be concerned about the Compositor getting idle.
We do still try to determine whether the Compositor is about to idle,
primarily, because the OpenGL render backend swaps buffers on present,
but that will change with the ongoing compositing timing rework.
2020-11-20 15:44:04 +00:00
|
|
|
std::chrono::milliseconds m_lastPresentTime;
|
2011-01-30 14:34:42 +00:00
|
|
|
QRect m_screenArea;
|
|
|
|
int m_activeScreen;
|
|
|
|
bool m_active;
|
|
|
|
bool m_start;
|
|
|
|
bool m_stop;
|
|
|
|
bool m_animation;
|
|
|
|
bool m_hasKeyboardGrab;
|
|
|
|
FlipSwitchMode m_mode;
|
|
|
|
EffectFrame* m_captionFrame;
|
|
|
|
QFont m_captionFont;
|
|
|
|
EffectWindowList m_flipOrderedWindows;
|
|
|
|
QHash< const EffectWindow*, ItemInfo* > m_windows;
|
2015-02-01 03:29:50 +00:00
|
|
|
QMatrix4x4 m_projectionMatrix;
|
|
|
|
QMatrix4x4 m_modelviewMatrix;
|
2011-01-30 14:34:42 +00:00
|
|
|
// options
|
|
|
|
bool m_tabbox;
|
|
|
|
bool m_tabboxAlternative;
|
|
|
|
float m_angle;
|
|
|
|
float m_xPosition;
|
|
|
|
float m_yPosition;
|
|
|
|
bool m_windowTitle;
|
|
|
|
// Shortcuts
|
2013-08-14 19:13:12 +00:00
|
|
|
QList<QKeySequence> m_shortcutCurrent;
|
|
|
|
QList<QKeySequence> m_shortcutAll;
|
2011-01-30 14:34:42 +00:00
|
|
|
};
|
2009-07-21 10:18:48 +00:00
|
|
|
|
|
|
|
class FlipSwitchEffect::ItemInfo
|
2011-01-30 14:34:42 +00:00
|
|
|
{
|
|
|
|
public:
|
|
|
|
ItemInfo();
|
|
|
|
~ItemInfo();
|
|
|
|
bool deleted;
|
|
|
|
double opacity;
|
|
|
|
double brightness;
|
|
|
|
double saturation;
|
|
|
|
};
|
2008-01-24 10:36:32 +00:00
|
|
|
|
|
|
|
} // namespace
|
|
|
|
|
|
|
|
#endif
|