2020-08-02 22:22:19 +00:00
|
|
|
/*
|
|
|
|
|
KWin - the KDE window manager
|
|
|
|
|
This file is part of the KDE project.
|
2007-04-29 17:35:43 +00:00
|
|
|
|
2020-08-02 22:22:19 +00:00
|
|
|
SPDX-FileCopyrightText: 2007 Lubos Lunak <l.lunak@kde.org>
|
|
|
|
|
SPDX-FileCopyrightText: 2008 Lucas Murray <lmurray@undefinedfire.com>
|
2007-04-29 17:35:43 +00:00
|
|
|
|
2020-08-02 22:22:19 +00:00
|
|
|
SPDX-License-Identifier: GPL-2.0-or-later
|
|
|
|
|
*/
|
2007-04-29 17:35:43 +00:00
|
|
|
|
|
|
|
|
#ifndef KWIN_DESKTOPGRID_H
|
|
|
|
|
#define KWIN_DESKTOPGRID_H
|
|
|
|
|
|
|
|
|
|
#include <kwineffects.h>
|
2008-02-02 20:54:19 +00:00
|
|
|
#include <QObject>
|
2013-02-26 08:00:51 +00:00
|
|
|
#include <QTimeLine>
|
2020-01-22 13:10:47 +00:00
|
|
|
|
2020-10-30 09:39:00 +00:00
|
|
|
class QTimer;
|
|
|
|
|
|
2020-01-22 13:10:47 +00:00
|
|
|
#include "kwineffectquickview.h"
|
2007-04-29 17:35:43 +00:00
|
|
|
|
|
|
|
|
namespace KWin
|
|
|
|
|
{
|
|
|
|
|
|
2009-11-15 12:38:26 +00:00
|
|
|
class PresentWindowsEffectProxy;
|
|
|
|
|
|
2007-04-29 17:35:43 +00:00
|
|
|
class DesktopGridEffect
|
2011-02-25 19:25:21 +00:00
|
|
|
: public Effect
|
2011-01-30 14:34:42 +00:00
|
|
|
{
|
2007-04-29 17:35:43 +00:00
|
|
|
Q_OBJECT
|
2012-08-11 09:24:37 +00:00
|
|
|
Q_PROPERTY(int zoomDuration READ configuredZoomDuration)
|
|
|
|
|
Q_PROPERTY(int border READ configuredBorder)
|
|
|
|
|
Q_PROPERTY(Qt::Alignment desktopNameAlignment READ configuredDesktopNameAlignment)
|
|
|
|
|
Q_PROPERTY(int layoutMode READ configuredLayoutMode)
|
|
|
|
|
Q_PROPERTY(int customLayoutRows READ configuredCustomLayoutRows)
|
|
|
|
|
Q_PROPERTY(bool usePresentWindows READ isUsePresentWindows)
|
|
|
|
|
// TODO: electric borders
|
2011-01-30 14:34:42 +00:00
|
|
|
public:
|
|
|
|
|
DesktopGridEffect();
|
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
|
|
|
~DesktopGridEffect() override;
|
|
|
|
|
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 windowInputMouseEvent(QEvent* e) override;
|
|
|
|
|
void grabbedKeyboardEvent(QKeyEvent* e) override;
|
|
|
|
|
bool borderActivated(ElectricBorder border) override;
|
|
|
|
|
bool isActive() const override;
|
2011-01-30 14:34:42 +00:00
|
|
|
|
2014-03-24 10:50:09 +00:00
|
|
|
int requestedEffectChainPosition() const override {
|
|
|
|
|
return 50;
|
|
|
|
|
}
|
|
|
|
|
|
2011-01-30 14:34:42 +00:00
|
|
|
enum { LayoutPager, LayoutAutomatic, LayoutCustom }; // Layout modes
|
2020-10-30 09:39:00 +00:00
|
|
|
enum { SwitchDesktopAndActivateWindow, SwitchDesktopOnly }; // Click behavior
|
2011-01-30 14:34:42 +00:00
|
|
|
|
2012-08-11 09:24:37 +00:00
|
|
|
// for properties
|
|
|
|
|
int configuredZoomDuration() const {
|
|
|
|
|
return zoomDuration;
|
|
|
|
|
}
|
|
|
|
|
int configuredBorder() const {
|
|
|
|
|
return border;
|
|
|
|
|
}
|
|
|
|
|
Qt::Alignment configuredDesktopNameAlignment() const {
|
|
|
|
|
return desktopNameAlignment;
|
|
|
|
|
}
|
|
|
|
|
int configuredLayoutMode() const {
|
|
|
|
|
return layoutMode;
|
|
|
|
|
}
|
|
|
|
|
int configuredCustomLayoutRows() const {
|
|
|
|
|
return customLayoutRows;
|
|
|
|
|
}
|
|
|
|
|
bool isUsePresentWindows() const {
|
2020-10-30 09:39:00 +00:00
|
|
|
return clickBehavior == SwitchDesktopAndActivateWindow;
|
2012-08-11 09:24:37 +00:00
|
|
|
}
|
2013-07-22 14:07:39 +00:00
|
|
|
private Q_SLOTS:
|
2011-01-30 14:34:42 +00:00
|
|
|
void toggle();
|
|
|
|
|
// slots for global shortcut changed
|
|
|
|
|
// needed to toggle the effect
|
2013-08-14 19:13:12 +00:00
|
|
|
void globalShortcutChanged(QAction *action, const QKeySequence& seq);
|
2011-01-30 14:34:42 +00:00
|
|
|
void slotAddDesktop();
|
|
|
|
|
void slotRemoveDesktop();
|
2012-01-29 11:29:24 +00:00
|
|
|
void slotWindowAdded(KWin::EffectWindow* w);
|
|
|
|
|
void slotWindowClosed(KWin::EffectWindow *w);
|
|
|
|
|
void slotWindowDeleted(KWin::EffectWindow *w);
|
2012-11-16 07:23:47 +00:00
|
|
|
void slotNumberDesktopsChanged(uint old);
|
2020-02-11 17:03:48 +00:00
|
|
|
void slotWindowFrameGeometryChanged(KWin::EffectWindow *w, const QRect &old);
|
2011-01-30 14:34:42 +00:00
|
|
|
|
|
|
|
|
private:
|
|
|
|
|
QPointF scalePos(const QPoint& pos, int desktop, int screen = -1) const;
|
Use nullptr everywhere
Summary:
Because KWin is a very old project, we use three kinds of null pointer
literals: 0, NULL, and nullptr. Since C++11, it's recommended to use
nullptr keyword.
This change converts all usages of 0 and NULL literal to nullptr. Even
though it breaks git history, we need to do it in order to have consistent
code as well to ease code reviews (it's very tempting for some people to
add unrelated changes to their patches, e.g. converting NULL to nullptr).
Test Plan: Compiles.
Reviewers: #kwin, davidedmundson, romangg
Reviewed By: #kwin, davidedmundson, romangg
Subscribers: romangg, kwin
Tags: #kwin
Differential Revision: https://phabricator.kde.org/D23618
2019-09-19 14:46:54 +00:00
|
|
|
QPoint unscalePos(const QPoint& pos, int* desktop = nullptr) const;
|
2011-01-30 14:34:42 +00:00
|
|
|
int posToDesktop(const QPoint& pos) const;
|
|
|
|
|
EffectWindow* windowAt(QPoint pos) const;
|
|
|
|
|
void setCurrentDesktop(int desktop);
|
|
|
|
|
void setHighlightedDesktop(int desktop);
|
|
|
|
|
int desktopToRight(int desktop, bool wrap = true) const;
|
|
|
|
|
int desktopToLeft(int desktop, bool wrap = true) const;
|
|
|
|
|
int desktopUp(int desktop, bool wrap = true) const;
|
|
|
|
|
int desktopDown(int desktop, bool wrap = true) const;
|
|
|
|
|
void setActive(bool active);
|
|
|
|
|
void setup();
|
|
|
|
|
void setupGrid();
|
|
|
|
|
void finish();
|
2011-08-27 09:21:31 +00:00
|
|
|
bool isMotionManagerMovingWindows() const;
|
2012-09-09 12:24:06 +00:00
|
|
|
bool isRelevantWithPresentWindows(EffectWindow *w) const;
|
2011-01-30 14:34:42 +00:00
|
|
|
bool isUsingPresentWindows() const;
|
|
|
|
|
QRectF moveGeometryToDesktop(int desktop) const;
|
|
|
|
|
void desktopsAdded(int old);
|
|
|
|
|
void desktopsRemoved(int old);
|
2015-09-14 14:40:31 +00:00
|
|
|
QVector<int> desktopList(const EffectWindow *w) const;
|
2011-01-30 14:34:42 +00:00
|
|
|
|
|
|
|
|
QList<ElectricBorder> borderActivate;
|
|
|
|
|
int zoomDuration;
|
|
|
|
|
int border;
|
|
|
|
|
Qt::Alignment desktopNameAlignment;
|
|
|
|
|
int layoutMode;
|
|
|
|
|
int customLayoutRows;
|
2020-10-30 09:39:00 +00:00
|
|
|
int clickBehavior;
|
2011-01-30 14:34:42 +00:00
|
|
|
|
|
|
|
|
bool activated;
|
2011-03-14 21:50:05 +00:00
|
|
|
QTimeLine timeline;
|
2011-01-30 14:34:42 +00:00
|
|
|
int paintingDesktop;
|
|
|
|
|
int highlightedDesktop;
|
[wayland] Use the new plasma virtual desktop protocol
Summary:
implement virtual desktop support for Wayland.
use the new virtual desktop protocol from D12820
The VirtualDesktopManager class needed some big change in order
to accomodate it, which is where most changes are.
Other than that, it's mostly connections to wire up
VirtualDesktopsManager and VirtualDesktopsManagement(the wayland protocol impl)
Depends on D12820
Other notable detail, is the client visibility updated to reflect the presence
of the client in the plasmavirtualdesktop.
(and the unSetDesktop concept)
Test Plan: used a bit a plasma session together with D12820, D13748 and D13746
Reviewers: #plasma, #kwin, graesslin, davidedmundson
Reviewed By: #plasma, #kwin, davidedmundson
Subscribers: hein, zzag, davidedmundson, kwin
Tags: #kwin
Maniphest Tasks: T4457
Differential Revision: https://phabricator.kde.org/D13887
2018-10-29 22:29:15 +00:00
|
|
|
int sourceDesktop;
|
2012-03-12 23:25:10 +00:00
|
|
|
int m_originalMovingDesktop;
|
2011-01-30 14:34:42 +00:00
|
|
|
bool keyboardGrab;
|
[wayland] Use the new plasma virtual desktop protocol
Summary:
implement virtual desktop support for Wayland.
use the new virtual desktop protocol from D12820
The VirtualDesktopManager class needed some big change in order
to accomodate it, which is where most changes are.
Other than that, it's mostly connections to wire up
VirtualDesktopsManager and VirtualDesktopsManagement(the wayland protocol impl)
Depends on D12820
Other notable detail, is the client visibility updated to reflect the presence
of the client in the plasmavirtualdesktop.
(and the unSetDesktop concept)
Test Plan: used a bit a plasma session together with D12820, D13748 and D13746
Reviewers: #plasma, #kwin, graesslin, davidedmundson
Reviewed By: #plasma, #kwin, davidedmundson
Subscribers: hein, zzag, davidedmundson, kwin
Tags: #kwin
Maniphest Tasks: T4457
Differential Revision: https://phabricator.kde.org/D13887
2018-10-29 22:29:15 +00:00
|
|
|
bool wasWindowMove, wasWindowCopy, wasDesktopMove, isValidMove;
|
2011-01-30 14:34:42 +00:00
|
|
|
EffectWindow* windowMove;
|
|
|
|
|
QPoint windowMoveDiff;
|
|
|
|
|
QPoint dragStartPos;
|
2020-10-30 09:39:00 +00:00
|
|
|
QTimer *windowMoveElevateTimer;
|
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 lastPresentTime;
|
2011-01-30 14:34:42 +00:00
|
|
|
|
|
|
|
|
// Soft highlighting
|
2011-03-14 21:50:05 +00:00
|
|
|
QList<QTimeLine*> hoverTimeline;
|
2011-01-30 14:34:42 +00:00
|
|
|
|
|
|
|
|
QList< EffectFrame* > desktopNames;
|
|
|
|
|
|
|
|
|
|
QSize gridSize;
|
|
|
|
|
Qt::Orientation orientation;
|
|
|
|
|
QPoint activeCell;
|
|
|
|
|
// Per screen variables
|
|
|
|
|
QList<double> scale; // Because the border isn't a ratio each screen is different
|
|
|
|
|
QList<double> unscaledBorder;
|
|
|
|
|
QList<QSizeF> scaledSize;
|
|
|
|
|
QList<QPointF> scaledOffset;
|
|
|
|
|
|
|
|
|
|
// Shortcut - needed to toggle the effect
|
2013-08-14 19:13:12 +00:00
|
|
|
QList<QKeySequence> shortcut;
|
2011-01-30 14:34:42 +00:00
|
|
|
|
|
|
|
|
PresentWindowsEffectProxy* m_proxy;
|
|
|
|
|
QList<WindowMotionManager> m_managers;
|
|
|
|
|
QRect m_windowMoveGeometry;
|
|
|
|
|
QPoint m_windowMoveStartPoint;
|
|
|
|
|
|
2020-01-22 13:10:47 +00:00
|
|
|
QVector<EffectQuickScene*> m_desktopButtons;
|
2011-01-30 14:34:42 +00:00
|
|
|
|
2017-04-01 17:30:44 +00:00
|
|
|
QAction *m_activateAction;
|
|
|
|
|
|
2011-01-30 14:34:42 +00:00
|
|
|
};
|
2007-04-29 17:35:43 +00:00
|
|
|
|
|
|
|
|
} // namespace
|
|
|
|
|
|
|
|
|
|
#endif
|
