2016-03-14 09:23:52 +00:00
|
|
|
/********************************************************************
|
|
|
|
KWin - the KDE window manager
|
|
|
|
This file is part of the KDE project.
|
|
|
|
|
|
|
|
Copyright (C) 2016 Martin Gräßlin <mgraesslin@kde.org>
|
|
|
|
|
|
|
|
This program is free software; you can redistribute it and/or modify
|
|
|
|
it under the terms of the GNU General Public License as published by
|
|
|
|
the Free Software Foundation; either version 2 of the License, or
|
|
|
|
(at your option) any later version.
|
|
|
|
|
|
|
|
This program is distributed in the hope that it will be useful,
|
|
|
|
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
GNU General Public License for more details.
|
|
|
|
|
|
|
|
You should have received a copy of the GNU General Public License
|
|
|
|
along with this program. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
*********************************************************************/
|
|
|
|
#ifndef KWIN_DEBUG_CONSOLE_H
|
|
|
|
#define KWIN_DEBUG_CONSOLE_H
|
|
|
|
|
|
|
|
#include <kwin_export.h>
|
[libinput] Add a wrapper class Device for a libinput_device
Summary:
The Device class wraps all the information we can get from libinput
about the device, like whether it's a keyboard, pointer, touch, etc.
In addition some more information is queried to figure out how "useful"
a device is. For a keyboard all alphanumeric keys are checked whether
they exist, for a pointer all (normal) buttons are queried.
All the information is exposed as Q_PROPERTY and used by the
DebugConsole. The DebugConsole gained a new tab "Input Devices" which
renders all devices and their properties in a tree view. When plugging
in/out a device, the model gets reset, so it's always up to date.
The new Device class can be used in future to configure the device,
e.g. disable touch pad, set mouse acceleration, etc.
Reviewers: #plasma
Subscribers: plasma-devel
Projects: #plasma
Differential Revision: https://phabricator.kde.org/D1538
2016-05-04 11:42:26 +00:00
|
|
|
#include <config-kwin.h>
|
2016-03-30 14:23:58 +00:00
|
|
|
#include "input.h"
|
2017-01-01 18:06:04 +00:00
|
|
|
#include "input_event_spy.h"
|
2016-03-14 09:23:52 +00:00
|
|
|
|
|
|
|
#include <QAbstractItemModel>
|
|
|
|
#include <QStyledItemDelegate>
|
|
|
|
#include <QVector>
|
|
|
|
|
2016-03-30 14:23:58 +00:00
|
|
|
class QTextEdit;
|
|
|
|
|
2016-03-14 09:23:52 +00:00
|
|
|
namespace Ui
|
|
|
|
{
|
|
|
|
class DebugConsole;
|
|
|
|
}
|
|
|
|
|
|
|
|
namespace KWin
|
|
|
|
{
|
|
|
|
|
2019-09-24 08:48:08 +00:00
|
|
|
class X11Client;
|
2019-08-26 07:44:04 +00:00
|
|
|
class InternalClient;
|
2019-08-30 21:36:58 +00:00
|
|
|
class XdgShellClient;
|
2016-03-14 09:23:52 +00:00
|
|
|
class Unmanaged;
|
2016-03-30 14:23:58 +00:00
|
|
|
class DebugConsoleFilter;
|
2016-03-14 09:23:52 +00:00
|
|
|
|
|
|
|
class KWIN_EXPORT DebugConsoleModel : public QAbstractItemModel
|
|
|
|
{
|
|
|
|
Q_OBJECT
|
|
|
|
public:
|
|
|
|
explicit DebugConsoleModel(QObject *parent = nullptr);
|
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
|
|
|
~DebugConsoleModel() override;
|
2016-03-14 09:23:52 +00:00
|
|
|
|
|
|
|
|
|
|
|
int columnCount(const QModelIndex &parent) const override;
|
|
|
|
QVariant data(const QModelIndex &index, int role) const override;
|
|
|
|
QModelIndex index(int row, int column, const QModelIndex & parent) const override;
|
|
|
|
int rowCount(const QModelIndex &parent) const override;
|
|
|
|
QModelIndex parent(const QModelIndex &child) const override;
|
|
|
|
|
|
|
|
private:
|
|
|
|
template <class T>
|
|
|
|
QModelIndex indexForClient(int row, int column, const QVector<T*> &clients, int id) const;
|
|
|
|
template <class T>
|
|
|
|
QModelIndex indexForProperty(int row, int column, const QModelIndex &parent, T *(DebugConsoleModel::*filter)(const QModelIndex&) const) const;
|
|
|
|
template <class T>
|
|
|
|
int propertyCount(const QModelIndex &parent, T *(DebugConsoleModel::*filter)(const QModelIndex&) const) const;
|
|
|
|
QVariant propertyData(QObject *object, const QModelIndex &index, int role) const;
|
|
|
|
template <class T>
|
|
|
|
QVariant clientData(const QModelIndex &index, int role, const QVector<T*> clients) const;
|
|
|
|
template <class T>
|
|
|
|
void add(int parentRow, QVector<T*> &clients, T *client);
|
|
|
|
template <class T>
|
|
|
|
void remove(int parentRow, QVector<T*> &clients, T *client);
|
2019-08-30 21:36:58 +00:00
|
|
|
XdgShellClient *shellClient(const QModelIndex &index) const;
|
2019-08-26 07:44:04 +00:00
|
|
|
InternalClient *internalClient(const QModelIndex &index) const;
|
2019-09-24 08:48:08 +00:00
|
|
|
X11Client *x11Client(const QModelIndex &index) const;
|
2016-03-14 09:23:52 +00:00
|
|
|
Unmanaged *unmanaged(const QModelIndex &index) const;
|
|
|
|
int topLevelRowCount() const;
|
|
|
|
|
2019-08-30 21:36:58 +00:00
|
|
|
QVector<XdgShellClient *> m_shellClients;
|
2019-08-26 07:44:04 +00:00
|
|
|
QVector<InternalClient*> m_internalClients;
|
2019-09-24 08:48:08 +00:00
|
|
|
QVector<X11Client *> m_x11Clients;
|
2016-03-14 09:23:52 +00:00
|
|
|
QVector<Unmanaged*> m_unmanageds;
|
|
|
|
|
|
|
|
};
|
|
|
|
|
|
|
|
class DebugConsoleDelegate : public QStyledItemDelegate
|
|
|
|
{
|
|
|
|
Q_OBJECT
|
|
|
|
public:
|
|
|
|
explicit DebugConsoleDelegate(QObject *parent = nullptr);
|
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
|
|
|
~DebugConsoleDelegate() override;
|
2016-03-14 09:23:52 +00:00
|
|
|
|
|
|
|
QString displayText(const QVariant &value, const QLocale &locale) const override;
|
|
|
|
};
|
|
|
|
|
2016-10-04 11:37:25 +00:00
|
|
|
class KWIN_EXPORT DebugConsole : public QWidget
|
2016-03-14 09:23:52 +00:00
|
|
|
{
|
|
|
|
Q_OBJECT
|
|
|
|
public:
|
|
|
|
DebugConsole();
|
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
|
|
|
~DebugConsole() override;
|
2016-03-14 09:23:52 +00:00
|
|
|
|
2016-10-04 12:06:01 +00:00
|
|
|
protected:
|
|
|
|
void showEvent(QShowEvent *event) override;
|
|
|
|
|
2016-03-14 09:23:52 +00:00
|
|
|
private:
|
2016-08-10 06:25:20 +00:00
|
|
|
void initGLTab();
|
2016-11-16 10:18:36 +00:00
|
|
|
void updateKeyboardTab();
|
2016-08-10 06:25:20 +00:00
|
|
|
|
2016-03-14 09:23:52 +00:00
|
|
|
QScopedPointer<Ui::DebugConsole> m_ui;
|
2016-03-30 14:23:58 +00:00
|
|
|
QScopedPointer<DebugConsoleFilter> m_inputFilter;
|
2016-03-14 09:23:52 +00:00
|
|
|
};
|
|
|
|
|
2016-03-23 10:25:58 +00:00
|
|
|
class SurfaceTreeModel : public QAbstractItemModel
|
|
|
|
{
|
|
|
|
Q_OBJECT
|
|
|
|
public:
|
|
|
|
explicit SurfaceTreeModel(QObject *parent = nullptr);
|
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
|
|
|
~SurfaceTreeModel() override;
|
2016-03-23 10:25:58 +00:00
|
|
|
|
|
|
|
int columnCount(const QModelIndex &parent) const override;
|
|
|
|
QVariant data(const QModelIndex &index, int role) const override;
|
|
|
|
QModelIndex index(int row, int column, const QModelIndex & parent) const override;
|
|
|
|
int rowCount(const QModelIndex &parent) const override;
|
|
|
|
QModelIndex parent(const QModelIndex &child) const override;
|
|
|
|
};
|
|
|
|
|
2017-01-01 18:06:04 +00:00
|
|
|
class DebugConsoleFilter : public InputEventSpy
|
2016-03-30 14:23:58 +00:00
|
|
|
{
|
|
|
|
public:
|
|
|
|
explicit DebugConsoleFilter(QTextEdit *textEdit);
|
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
|
|
|
~DebugConsoleFilter() override;
|
2016-03-30 14:23:58 +00:00
|
|
|
|
2017-01-01 18:06:04 +00:00
|
|
|
void pointerEvent(MouseEvent *event) override;
|
|
|
|
void wheelEvent(WheelEvent *event) override;
|
|
|
|
void keyEvent(KeyEvent *event) override;
|
2019-08-11 19:57:45 +00:00
|
|
|
void touchDown(qint32 id, const QPointF &pos, quint32 time) override;
|
|
|
|
void touchMotion(qint32 id, const QPointF &pos, quint32 time) override;
|
|
|
|
void touchUp(qint32 id, quint32 time) override;
|
2017-01-01 18:06:04 +00:00
|
|
|
|
|
|
|
void pinchGestureBegin(int fingerCount, quint32 time) override;
|
|
|
|
void pinchGestureUpdate(qreal scale, qreal angleDelta, const QSizeF &delta, quint32 time) override;
|
|
|
|
void pinchGestureEnd(quint32 time) override;
|
|
|
|
void pinchGestureCancelled(quint32 time) override;
|
|
|
|
|
|
|
|
void swipeGestureBegin(int fingerCount, quint32 time) override;
|
|
|
|
void swipeGestureUpdate(const QSizeF &delta, quint32 time) override;
|
|
|
|
void swipeGestureEnd(quint32 time) override;
|
|
|
|
void swipeGestureCancelled(quint32 time) override;
|
2016-08-05 12:35:33 +00:00
|
|
|
|
2017-12-27 19:25:36 +00:00
|
|
|
void switchEvent(SwitchEvent *event) override;
|
|
|
|
|
2016-03-30 14:23:58 +00:00
|
|
|
private:
|
|
|
|
QTextEdit *m_textEdit;
|
|
|
|
};
|
|
|
|
|
2016-05-06 12:48:25 +00:00
|
|
|
namespace LibInput
|
|
|
|
{
|
|
|
|
class Device;
|
|
|
|
}
|
|
|
|
|
[libinput] Add a wrapper class Device for a libinput_device
Summary:
The Device class wraps all the information we can get from libinput
about the device, like whether it's a keyboard, pointer, touch, etc.
In addition some more information is queried to figure out how "useful"
a device is. For a keyboard all alphanumeric keys are checked whether
they exist, for a pointer all (normal) buttons are queried.
All the information is exposed as Q_PROPERTY and used by the
DebugConsole. The DebugConsole gained a new tab "Input Devices" which
renders all devices and their properties in a tree view. When plugging
in/out a device, the model gets reset, so it's always up to date.
The new Device class can be used in future to configure the device,
e.g. disable touch pad, set mouse acceleration, etc.
Reviewers: #plasma
Subscribers: plasma-devel
Projects: #plasma
Differential Revision: https://phabricator.kde.org/D1538
2016-05-04 11:42:26 +00:00
|
|
|
class InputDeviceModel : public QAbstractItemModel
|
|
|
|
{
|
|
|
|
Q_OBJECT
|
|
|
|
public:
|
|
|
|
explicit InputDeviceModel(QObject *parent = nullptr);
|
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
|
|
|
~InputDeviceModel() override;
|
[libinput] Add a wrapper class Device for a libinput_device
Summary:
The Device class wraps all the information we can get from libinput
about the device, like whether it's a keyboard, pointer, touch, etc.
In addition some more information is queried to figure out how "useful"
a device is. For a keyboard all alphanumeric keys are checked whether
they exist, for a pointer all (normal) buttons are queried.
All the information is exposed as Q_PROPERTY and used by the
DebugConsole. The DebugConsole gained a new tab "Input Devices" which
renders all devices and their properties in a tree view. When plugging
in/out a device, the model gets reset, so it's always up to date.
The new Device class can be used in future to configure the device,
e.g. disable touch pad, set mouse acceleration, etc.
Reviewers: #plasma
Subscribers: plasma-devel
Projects: #plasma
Differential Revision: https://phabricator.kde.org/D1538
2016-05-04 11:42:26 +00:00
|
|
|
|
|
|
|
int columnCount(const QModelIndex &parent) const override;
|
|
|
|
QVariant data(const QModelIndex &index, int role) const override;
|
|
|
|
QModelIndex index(int row, int column, const QModelIndex & parent) const override;
|
|
|
|
int rowCount(const QModelIndex &parent) const override;
|
|
|
|
QModelIndex parent(const QModelIndex &child) const override;
|
2016-05-06 12:48:25 +00:00
|
|
|
|
|
|
|
private:
|
|
|
|
void setupDeviceConnections(LibInput::Device *device);
|
|
|
|
QVector<LibInput::Device*> m_devices;
|
[libinput] Add a wrapper class Device for a libinput_device
Summary:
The Device class wraps all the information we can get from libinput
about the device, like whether it's a keyboard, pointer, touch, etc.
In addition some more information is queried to figure out how "useful"
a device is. For a keyboard all alphanumeric keys are checked whether
they exist, for a pointer all (normal) buttons are queried.
All the information is exposed as Q_PROPERTY and used by the
DebugConsole. The DebugConsole gained a new tab "Input Devices" which
renders all devices and their properties in a tree view. When plugging
in/out a device, the model gets reset, so it's always up to date.
The new Device class can be used in future to configure the device,
e.g. disable touch pad, set mouse acceleration, etc.
Reviewers: #plasma
Subscribers: plasma-devel
Projects: #plasma
Differential Revision: https://phabricator.kde.org/D1538
2016-05-04 11:42:26 +00:00
|
|
|
};
|
|
|
|
|
2016-03-14 09:23:52 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
#endif
|