2021-01-01 16:55:44 +00:00
|
|
|
// SPDX-License-Identifier: GPL-2.0
|
|
|
|
// A legend box, which is shown on the chart.
|
|
|
|
#ifndef STATS_LEGEND_H
|
|
|
|
#define STATS_LEGEND_H
|
|
|
|
|
2021-01-03 11:49:26 +00:00
|
|
|
#include "backend-shared/roundrectitem.h"
|
|
|
|
|
2021-01-01 16:55:44 +00:00
|
|
|
#include <memory>
|
|
|
|
#include <vector>
|
|
|
|
|
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
|
|
|
class QGraphicsScene;
|
2021-01-01 16:55:44 +00:00
|
|
|
class QGraphicsSceneMouseEvent;
|
|
|
|
|
2021-01-03 11:49:26 +00:00
|
|
|
class Legend : public RoundRectItem {
|
2021-01-01 16:55:44 +00:00
|
|
|
public:
|
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
|
|
|
Legend(const std::vector<QString> &names);
|
2021-01-01 16:55:44 +00:00
|
|
|
void hover(QPointF pos);
|
|
|
|
void resize(); // called when the chart size changes.
|
|
|
|
private:
|
|
|
|
// Each entry is a text besides a rectangle showing the color
|
|
|
|
struct Entry {
|
|
|
|
std::unique_ptr<QGraphicsRectItem> rect;
|
|
|
|
std::unique_ptr<QGraphicsSimpleTextItem> text;
|
|
|
|
QPointF pos;
|
|
|
|
double width;
|
|
|
|
Entry(const QString &name, int idx, int numBins, QGraphicsItem *parent);
|
|
|
|
};
|
|
|
|
int displayedItems;
|
|
|
|
double width;
|
|
|
|
double height;
|
|
|
|
int fontHeight;
|
|
|
|
std::vector<Entry> entries;
|
|
|
|
void updatePosition();
|
|
|
|
void hide();
|
|
|
|
};
|
|
|
|
|
|
|
|
#endif
|