statistics: convert chart to QQuickItem
It turns out that the wrong base class was used for the chart.
QQuickWidget can only be used on desktop, not in a mobile UI.
Therefore, turn this into a QQuickItem and move the container
QQuickWidget into desktop-only code.
Currently, this code is insane: The chart is rendered onto a
QGraphicsScene (as it was before), which is then rendered into
a QImage, which is transformed into a QSGTexture, which is then
projected onto the device. This is performed on every mouse
move event, since these events in general change the position
of the info-box.
The plan is to slowly convert elements such as the info-box into
QQuickItems. Browsing the QtQuick documentation, this will
not be much fun.
Also note that the rendering currently tears, flickers and has
antialiasing artifacts, most likely owing to integer (QImage)
to floating point (QGraphicsScene, QQuickItem) conversion
problems. The data flow is
QGraphicsScene (float) -> QImage (int) -> QQuickItem (float).
Signed-off-by: Berthold Stoeger <bstoeger@mail.tuwien.ac.at>
2021-01-07 13:38:37 +00:00
|
|
|
// SPDX-License-Identifier: GPL-2.0
|
2021-01-18 12:14:38 +00:00
|
|
|
// Helper functions to render the stats. Currently contains
|
|
|
|
// QSGNode template jugglery to overcome API flaws.
|
statistics: convert chart to QQuickItem
It turns out that the wrong base class was used for the chart.
QQuickWidget can only be used on desktop, not in a mobile UI.
Therefore, turn this into a QQuickItem and move the container
QQuickWidget into desktop-only code.
Currently, this code is insane: The chart is rendered onto a
QGraphicsScene (as it was before), which is then rendered into
a QImage, which is transformed into a QSGTexture, which is then
projected onto the device. This is performed on every mouse
move event, since these events in general change the position
of the info-box.
The plan is to slowly convert elements such as the info-box into
QQuickItems. Browsing the QtQuick documentation, this will
not be much fun.
Also note that the rendering currently tears, flickers and has
antialiasing artifacts, most likely owing to integer (QImage)
to floating point (QGraphicsScene, QQuickItem) conversion
problems. The data flow is
QGraphicsScene (float) -> QImage (int) -> QQuickItem (float).
Signed-off-by: Berthold Stoeger <bstoeger@mail.tuwien.ac.at>
2021-01-07 13:38:37 +00:00
|
|
|
#ifndef STATSHELPER_H
|
2021-01-17 17:29:54 +00:00
|
|
|
#define STATSHELPER_H
|
statistics: convert chart to QQuickItem
It turns out that the wrong base class was used for the chart.
QQuickWidget can only be used on desktop, not in a mobile UI.
Therefore, turn this into a QQuickItem and move the container
QQuickWidget into desktop-only code.
Currently, this code is insane: The chart is rendered onto a
QGraphicsScene (as it was before), which is then rendered into
a QImage, which is transformed into a QSGTexture, which is then
projected onto the device. This is performed on every mouse
move event, since these events in general change the position
of the info-box.
The plan is to slowly convert elements such as the info-box into
QQuickItems. Browsing the QtQuick documentation, this will
not be much fun.
Also note that the rendering currently tears, flickers and has
antialiasing artifacts, most likely owing to integer (QImage)
to floating point (QGraphicsScene, QQuickItem) conversion
problems. The data flow is
QGraphicsScene (float) -> QImage (int) -> QQuickItem (float).
Signed-off-by: Berthold Stoeger <bstoeger@mail.tuwien.ac.at>
2021-01-07 13:38:37 +00:00
|
|
|
|
|
|
|
#include <memory>
|
2021-01-17 17:29:54 +00:00
|
|
|
#include <QSGNode>
|
statistics: convert chart to QQuickItem
It turns out that the wrong base class was used for the chart.
QQuickWidget can only be used on desktop, not in a mobile UI.
Therefore, turn this into a QQuickItem and move the container
QQuickWidget into desktop-only code.
Currently, this code is insane: The chart is rendered onto a
QGraphicsScene (as it was before), which is then rendered into
a QImage, which is transformed into a QSGTexture, which is then
projected onto the device. This is performed on every mouse
move event, since these events in general change the position
of the info-box.
The plan is to slowly convert elements such as the info-box into
QQuickItems. Browsing the QtQuick documentation, this will
not be much fun.
Also note that the rendering currently tears, flickers and has
antialiasing artifacts, most likely owing to integer (QImage)
to floating point (QGraphicsScene, QQuickItem) conversion
problems. The data flow is
QGraphicsScene (float) -> QImage (int) -> QQuickItem (float).
Signed-off-by: Berthold Stoeger <bstoeger@mail.tuwien.ac.at>
2021-01-07 13:38:37 +00:00
|
|
|
|
2021-01-17 17:29:54 +00:00
|
|
|
// In general, we want chart items to be hideable. For example to show/hide
|
|
|
|
// labels on demand. Very sadly, the QSG API is absolutely terrible with
|
|
|
|
// respect to temporarily disabling. Instead of simply having a flag,
|
|
|
|
// a QSGNode is queried using the "isSubtreeBlocked()" virtual function(!).
|
|
|
|
//
|
|
|
|
// Not only is this a slow operation performed on every single node, it
|
|
|
|
// also is often not possible to override this function: For improved
|
|
|
|
// performance, the documentation recommends to create QSG nodes via
|
|
|
|
// QQuickWindow. This provides nodes optimized for the actual hardware.
|
|
|
|
// However, this obviously means that these nodes cannot be derived from!
|
|
|
|
//
|
|
|
|
// In that case, there are two possibilities: Add a proxy node with an
|
|
|
|
// overridden "isSubtreeBlocked()" function or remove the node from the
|
|
|
|
// scene. The former was chosen here, because it is less complex.
|
|
|
|
//
|
|
|
|
// The following slightly cryptic templates are used to unify the two
|
|
|
|
// cases: The QSGNode is generated by our own code or the QSGNode is
|
|
|
|
// obtained from QQuickWindow.
|
|
|
|
//
|
|
|
|
// The "HideableQSGNode<Node>" template augments the QSGNode "Node"
|
|
|
|
// by a "setVisible()" function and overrides "isSubtreeBlocked()"
|
|
|
|
//
|
|
|
|
// The "QSGProxyNode<Node>" template is a QSGNode with a single
|
|
|
|
// child of type "Node".
|
|
|
|
//
|
|
|
|
// Thus, if the node can be created, use:
|
|
|
|
// HideableQSGNode<NodeTypeThatCanBeCreated> node
|
|
|
|
// and if the node can only be obtained from QQuickWindow, use:
|
|
|
|
// HideableQSGNode<QSGProxyNode<NodeThatCantBeCreated>> node
|
|
|
|
// The latter should obviously be typedef-ed.
|
|
|
|
//
|
|
|
|
// Yes, that's all horrible, but if nothing else it teaches us about
|
|
|
|
// composition.
|
|
|
|
template <typename Node>
|
|
|
|
class HideableQSGNode : public Node {
|
|
|
|
bool hidden;
|
|
|
|
bool isSubtreeBlocked() const override final;
|
|
|
|
public:
|
|
|
|
template<class... Args>
|
|
|
|
HideableQSGNode(bool visible, Args&&... args);
|
|
|
|
void setVisible(bool visible);
|
|
|
|
};
|
|
|
|
|
|
|
|
template <typename Node>
|
|
|
|
class QSGProxyNode : public QSGNode {
|
|
|
|
public:
|
|
|
|
std::unique_ptr<Node> node;
|
|
|
|
QSGProxyNode(Node *node);
|
|
|
|
};
|
|
|
|
|
|
|
|
// Implementation detail of templates - move to serparate header file
|
|
|
|
template <typename Node>
|
|
|
|
QSGProxyNode<Node>::QSGProxyNode(Node *node) : node(node)
|
|
|
|
{
|
|
|
|
appendChildNode(node);
|
|
|
|
}
|
|
|
|
|
|
|
|
template <typename Node>
|
|
|
|
bool HideableQSGNode<Node>::isSubtreeBlocked() const
|
|
|
|
{
|
|
|
|
return hidden;
|
|
|
|
}
|
|
|
|
|
|
|
|
template <typename Node>
|
|
|
|
template<class... Args>
|
|
|
|
HideableQSGNode<Node>::HideableQSGNode(bool visible, Args&&... args) :
|
|
|
|
Node(std::forward<Args>(args)...),
|
|
|
|
hidden(!visible)
|
|
|
|
{
|
|
|
|
}
|
|
|
|
|
|
|
|
template <typename Node>
|
|
|
|
void HideableQSGNode<Node>::setVisible(bool visible)
|
|
|
|
{
|
|
|
|
hidden = !visible;
|
|
|
|
}
|
|
|
|
|
statistics: convert chart to QQuickItem
It turns out that the wrong base class was used for the chart.
QQuickWidget can only be used on desktop, not in a mobile UI.
Therefore, turn this into a QQuickItem and move the container
QQuickWidget into desktop-only code.
Currently, this code is insane: The chart is rendered onto a
QGraphicsScene (as it was before), which is then rendered into
a QImage, which is transformed into a QSGTexture, which is then
projected onto the device. This is performed on every mouse
move event, since these events in general change the position
of the info-box.
The plan is to slowly convert elements such as the info-box into
QQuickItems. Browsing the QtQuick documentation, this will
not be much fun.
Also note that the rendering currently tears, flickers and has
antialiasing artifacts, most likely owing to integer (QImage)
to floating point (QGraphicsScene, QQuickItem) conversion
problems. The data flow is
QGraphicsScene (float) -> QImage (int) -> QQuickItem (float).
Signed-off-by: Berthold Stoeger <bstoeger@mail.tuwien.ac.at>
2021-01-07 13:38:37 +00:00
|
|
|
#endif
|