2020-08-02 22:22:19 +00:00
|
|
|
/*
|
|
|
|
KWin - the KDE window manager
|
|
|
|
This file is part of the KDE project.
|
2013-06-21 08:03:31 +00:00
|
|
|
|
2020-08-02 22:22:19 +00:00
|
|
|
SPDX-FileCopyrightText: 2013 Martin Gräßlin <mgraesslin@kde.org>
|
2013-06-21 08:03:31 +00:00
|
|
|
|
2020-08-02 22:22:19 +00:00
|
|
|
SPDX-License-Identifier: GPL-2.0-or-later
|
|
|
|
*/
|
2013-06-21 08:03:31 +00:00
|
|
|
#ifndef KWIN_SCENE_QPAINTER_H
|
|
|
|
#define KWIN_SCENE_QPAINTER_H
|
|
|
|
|
|
|
|
#include "scene.h"
|
2017-08-11 19:40:49 +00:00
|
|
|
#include <platformsupport/scenes/qpainter/backend.h>
|
2013-06-21 08:03:31 +00:00
|
|
|
#include "shadow.h"
|
|
|
|
|
2014-07-22 11:11:19 +00:00
|
|
|
#include "decorations/decorationrenderer.h"
|
|
|
|
|
2013-06-21 08:03:31 +00:00
|
|
|
namespace KWin {
|
|
|
|
|
2016-06-29 17:22:41 +00:00
|
|
|
class KWIN_EXPORT SceneQPainter : public Scene
|
2013-06-21 08:03:31 +00:00
|
|
|
{
|
|
|
|
Q_OBJECT
|
|
|
|
|
|
|
|
public:
|
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
|
|
|
~SceneQPainter() override;
|
|
|
|
bool usesOverlayWindow() const override;
|
2019-08-07 17:33:20 +00:00
|
|
|
OverlayWindow* overlayWindow() const 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 paint(int screenId, const QRegion &damage, const QList<Toplevel *> &windows,
|
|
|
|
std::chrono::milliseconds presentTime) override;
|
2020-03-13 16:41:56 +00:00
|
|
|
void paintGenericScreen(int mask, const 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
|
|
|
CompositingType compositingType() const override;
|
|
|
|
bool initFailed() const override;
|
|
|
|
EffectFrame *createEffectFrame(EffectFrameImpl *frame) override;
|
|
|
|
Shadow *createShadow(Toplevel *toplevel) override;
|
2014-07-22 11:11:19 +00:00
|
|
|
Decoration::Renderer *createDecorationRenderer(Decoration::DecoratedClientImpl *impl) override;
|
2015-03-19 07:29:34 +00:00
|
|
|
void screenGeometryChanged(const QSize &size) override;
|
2013-06-21 08:03:31 +00:00
|
|
|
|
2016-08-10 07:24:53 +00:00
|
|
|
bool animationsSupported() const override {
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
2017-08-09 04:56:23 +00:00
|
|
|
QPainter *scenePainter() const override;
|
2020-11-09 13:39:36 +00:00
|
|
|
QImage *qpainterRenderBuffer(int screenId) const override;
|
2013-06-21 08:03:31 +00:00
|
|
|
|
2016-06-29 17:22:41 +00:00
|
|
|
QPainterBackend *backend() const {
|
|
|
|
return m_backend.data();
|
|
|
|
}
|
|
|
|
|
2015-02-23 13:41:45 +00:00
|
|
|
static SceneQPainter *createScene(QObject *parent);
|
2013-06-21 08:03:31 +00:00
|
|
|
|
|
|
|
protected:
|
2020-03-13 16:41:56 +00:00
|
|
|
void paintBackground(const QRegion ®ion) 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
|
|
|
Scene::Window *createWindow(Toplevel *toplevel) override;
|
2020-10-26 07:39:55 +00:00
|
|
|
void paintCursor(const QRegion ®ion) override;
|
[libkwineffects] Introduce API to easily show a QtQuick scene in an effect
Summary:
EffectQuickView/Scene is a convenient class to render a QtQuick
scenegraph into an effect.
Current methods (such as present windows) involve creating an underlying
platform window which is expensive, causes a headache to filter out
again in the rest of the code, and only works as an overlay.
The new class exposes things more natively to an effect where we don't
mess with real windows, we can perform the painting anywhere in the view
and we don't have issues with hiding/closing.
QtQuick has both software and hardware accelerated modes, and kwin also
has 3 render backends. Every combination is supported.
* When used in OpenGL mode for both, we render into an FBO export the
texture ID then it's up to the effect to render that into a scene.
* When using software QtQuick rendering we blit into an image, upload
that into a KWinGLTexture which serves as an abstraction layer and
render that into the scene.
* When using GL for QtQuick and XRender/QPainter in kwin everything is
rendered into the internal FBO, blit and exported as an image.
* When using software rendering for both an image gets passed directly.
Mouse and keyboard events can be forwarded, only if the effect
intercepts them.
The class is meant to be generic enough that we can remove all the
QtQuick code from Aurorae.
The intention is also to replace EffectFrameImpl using this backend and
we can kill all of the EffectFrame code throughout the scenes.
The close button in present windows will also be ported to this,
simplifiying that code base.
Classes that handle the rendering and handling QML are intentionally
split so that in the future we can have a declarative effects API create
overlays from within the same context. Similar to how one can
instantiate windows from a typical QML scene.
Notes:
I don't like how I pass the kwin GL context from the backends into the
effect, but I need something that works with the library separation. It
also currently has wayland problem if I create a QOpenGLContext before
the QPA is set up with a scene - but I don't have anything better?
I know for the EffectFrame we need an API to push things through the
effects stack to handle blur/invert etc. Will deal with that when we
port the EffectFrame.
Test Plan: Used in an effect
Reviewers: #kwin, zzag
Reviewed By: #kwin, zzag
Subscribers: zzag, kwin
Tags: #kwin
Differential Revision: https://phabricator.kde.org/D24215
2019-09-27 15:06:37 +00:00
|
|
|
void paintEffectQuickView(EffectQuickView *w) override;
|
2013-06-21 08:03:31 +00:00
|
|
|
|
|
|
|
private:
|
2015-02-23 13:41:45 +00:00
|
|
|
explicit SceneQPainter(QPainterBackend *backend, QObject *parent = nullptr);
|
2013-06-21 08:03:31 +00:00
|
|
|
QScopedPointer<QPainterBackend> m_backend;
|
|
|
|
QScopedPointer<QPainter> m_painter;
|
|
|
|
class Window;
|
|
|
|
};
|
|
|
|
|
|
|
|
class QPainterWindowPixmap : public WindowPixmap
|
|
|
|
{
|
|
|
|
public:
|
|
|
|
explicit QPainterWindowPixmap(Scene::Window *window);
|
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
|
|
|
~QPainterWindowPixmap() override;
|
|
|
|
void create() override;
|
2020-04-21 08:55:51 +00:00
|
|
|
void update() override;
|
2016-09-09 07:41:05 +00:00
|
|
|
bool isValid() const override;
|
2013-06-21 08:03:31 +00:00
|
|
|
|
|
|
|
const QImage &image();
|
2016-03-21 15:42:30 +00:00
|
|
|
|
|
|
|
protected:
|
2020-10-31 15:09:34 +00:00
|
|
|
WindowPixmap *createChild(KWaylandServer::SubSurfaceInterface *subSurface) override;
|
2013-06-21 08:03:31 +00:00
|
|
|
private:
|
2020-10-31 15:09:34 +00:00
|
|
|
explicit QPainterWindowPixmap(KWaylandServer::SubSurfaceInterface *subSurface, WindowPixmap *parent);
|
2013-06-21 08:03:31 +00:00
|
|
|
QImage m_image;
|
|
|
|
};
|
|
|
|
|
2020-05-23 15:07:54 +00:00
|
|
|
class SceneQPainter::Window : public Scene::Window
|
|
|
|
{
|
2020-06-10 06:13:35 +00:00
|
|
|
Q_OBJECT
|
|
|
|
|
2020-05-23 15:07:54 +00:00
|
|
|
public:
|
|
|
|
Window(SceneQPainter *scene, Toplevel *c);
|
|
|
|
~Window() override;
|
|
|
|
void performPaint(int mask, const QRegion ®ion, const WindowPaintData &data) override;
|
|
|
|
protected:
|
|
|
|
WindowPixmap *createWindowPixmap() override;
|
|
|
|
private:
|
|
|
|
void renderWindowPixmap(QPainter *painter, QPainterWindowPixmap *windowPixmap);
|
|
|
|
void renderShadow(QPainter *painter);
|
|
|
|
void renderWindowDecorations(QPainter *painter);
|
|
|
|
SceneQPainter *m_scene;
|
|
|
|
};
|
|
|
|
|
2013-06-21 08:03:31 +00:00
|
|
|
class QPainterEffectFrame : public Scene::EffectFrame
|
|
|
|
{
|
|
|
|
public:
|
|
|
|
QPainterEffectFrame(EffectFrameImpl *frame, SceneQPainter *scene);
|
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
|
|
|
~QPainterEffectFrame() override;
|
|
|
|
void crossFadeIcon() override {}
|
|
|
|
void crossFadeText() override {}
|
|
|
|
void free() override {}
|
|
|
|
void freeIconFrame() override {}
|
|
|
|
void freeTextFrame() override {}
|
|
|
|
void freeSelection() override {}
|
2020-03-13 16:41:56 +00:00
|
|
|
void render(const QRegion ®ion, double opacity, double frameOpacity) override;
|
2013-06-21 08:03:31 +00:00
|
|
|
private:
|
|
|
|
SceneQPainter *m_scene;
|
|
|
|
};
|
|
|
|
|
|
|
|
class SceneQPainterShadow : public Shadow
|
|
|
|
{
|
|
|
|
public:
|
|
|
|
SceneQPainterShadow(Toplevel* toplevel);
|
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
|
|
|
~SceneQPainterShadow() override;
|
2018-06-07 09:08:15 +00:00
|
|
|
|
|
|
|
QImage &shadowTexture() {
|
|
|
|
return m_texture;
|
|
|
|
}
|
|
|
|
|
2013-06-21 08:03:31 +00:00
|
|
|
protected:
|
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 buildQuads() override;
|
|
|
|
bool prepareBackend() override;
|
2018-06-07 09:08:15 +00:00
|
|
|
|
|
|
|
private:
|
|
|
|
QImage m_texture;
|
2013-06-21 08:03:31 +00:00
|
|
|
};
|
|
|
|
|
2014-07-22 11:11:19 +00:00
|
|
|
class SceneQPainterDecorationRenderer : public Decoration::Renderer
|
|
|
|
{
|
|
|
|
Q_OBJECT
|
|
|
|
public:
|
|
|
|
enum class DecorationPart : int {
|
|
|
|
Left,
|
|
|
|
Top,
|
|
|
|
Right,
|
|
|
|
Bottom,
|
|
|
|
Count
|
|
|
|
};
|
|
|
|
explicit SceneQPainterDecorationRenderer(Decoration::DecoratedClientImpl *client);
|
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
|
|
|
~SceneQPainterDecorationRenderer() override;
|
2014-07-22 11:11:19 +00:00
|
|
|
|
|
|
|
void render() override;
|
2014-07-23 07:20:28 +00:00
|
|
|
void reparent(Deleted *deleted) override;
|
2014-07-22 11:11:19 +00:00
|
|
|
|
|
|
|
QImage image(DecorationPart part) const;
|
|
|
|
|
|
|
|
private:
|
|
|
|
void resizeImages();
|
|
|
|
QImage m_images[int(DecorationPart::Count)];
|
|
|
|
};
|
|
|
|
|
2017-08-11 19:40:49 +00:00
|
|
|
class KWIN_EXPORT QPainterFactory : public SceneFactory
|
|
|
|
{
|
|
|
|
Q_OBJECT
|
|
|
|
Q_INTERFACES(KWin::SceneFactory)
|
|
|
|
Q_PLUGIN_METADATA(IID "org.kde.kwin.Scene" FILE "qpainter.json")
|
|
|
|
|
|
|
|
public:
|
|
|
|
explicit QPainterFactory(QObject *parent = nullptr);
|
|
|
|
~QPainterFactory() override;
|
|
|
|
|
|
|
|
Scene *create(QObject *parent = nullptr) const override;
|
|
|
|
};
|
|
|
|
|
2013-06-21 08:03:31 +00:00
|
|
|
inline
|
|
|
|
bool SceneQPainter::usesOverlayWindow() const
|
|
|
|
{
|
2020-11-09 13:11:58 +00:00
|
|
|
return false;
|
2013-06-21 08:03:31 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
inline
|
2019-08-07 17:33:20 +00:00
|
|
|
OverlayWindow* SceneQPainter::overlayWindow() const
|
2013-06-21 08:03:31 +00:00
|
|
|
{
|
2020-11-09 13:11:58 +00:00
|
|
|
return nullptr;
|
2013-06-21 08:03:31 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
inline
|
2017-08-09 04:56:23 +00:00
|
|
|
QPainter* SceneQPainter::scenePainter() const
|
2013-06-21 08:03:31 +00:00
|
|
|
{
|
|
|
|
return m_painter.data();
|
|
|
|
}
|
|
|
|
|
|
|
|
inline
|
|
|
|
const QImage &QPainterWindowPixmap::image()
|
|
|
|
{
|
|
|
|
return m_image;
|
|
|
|
}
|
|
|
|
|
|
|
|
} // KWin
|
|
|
|
|
|
|
|
#endif // KWIN_SCENEQPAINTER_H
|