Support data range selection in livreGUI #382
Conversation
tribal-tec
commented
Mar 2, 2017
tribal-tec
commented
- Publish new lexix/materialLUT event which contains data range
- Still publishes 'old' lexis/lookupTable1D
- Overhaul of the transfer function widgets; now uses QML to draw everything
|
|
| #include <QQuickItem> | ||
| #include <QVector4D> | ||
|
|
||
| const QUrl QML_ROOT_COMPONENT( "qrc:/qml/AlphaWidget.qml" ); |
| // convert the gradient stops to something that QML understands | ||
| QList< QVariant > positions; | ||
| QList< QVariant > colors; | ||
| for( auto& stop: stops ) |
| property var positions: [] | ||
| property alias controlpoints: controlpoints.controlpoints | ||
|
|
||
| // interestingly enough there is no proper way to dynamically update |
There was a problem hiding this comment.
seriously, changing the stops of the gradient does not update it? That's terrible :-(
There was a problem hiding this comment.
I couldn't find a programmatic way of updating/adding gradient stops...
There was a problem hiding this comment.
yes, the stops property is read-only, no other option.
| anchors.fill: parent | ||
| start: Qt.point(0, 0) | ||
| end: Qt.point(parent.width, 0) | ||
| gradient: root.gradient |
There was a problem hiding this comment.
does gradient have to be a property of root? Can't it be defined here directly?
There was a problem hiding this comment.
Mainly for easier access from C++ side, unless you meant something else.
There was a problem hiding this comment.
yes, that's what I meant, I would have expected a property alias at the root instead of the other way around. Don't know if that works from C++ though. As it is now, it looks like an artifact linked to the onColorsChanged() magic.
| import QtQuick 2.0 | ||
| import "qrc:/qml/style.js" as Style | ||
|
|
||
| Item { |
| { | ||
| case Channel::red: color = Qt::red; break; | ||
| case Channel::green: color = Qt::green; break; | ||
| case Channel::blue: default: color = Qt::blue; |
There was a problem hiding this comment.
the switch is a copy-paste from above, could be a helper function
| import QtQuick 2.0 | ||
| import "qrc:/qml/style.js" as Style | ||
|
|
||
| Item { |
| _ui->background->installEventFilter( this ); | ||
| _ui->background->rootContext()->setContextProperty( "model", this ); | ||
|
|
||
| connect( _ui->fitToDataButton, &QPushButton::clicked, [&] |
There was a problem hiding this comment.
although the result is the same, it would be enough for all the lambdas in this function to capture [this] instead of [&]
|
|
||
| void RangeWidget::setRangeX(qreal rangeX) | ||
| { | ||
| if( std::abs( _rangeX - rangeX ) <= 0.0001 ) |
There was a problem hiding this comment.
or use qFuzzyCompare( _rangeX, rangeX )
There was a problem hiding this comment.
Yes, it's also good to know that it's used internally by the QRectF / QsizeF == operators
| return false; | ||
| } | ||
|
|
||
| void RangeWidget::setRangeX(qreal rangeX) |
* Publish new lexix/materialLUT event which contains data range * Still publishes 'old' lexis/lookupTable1D * Overhaul of the transfer function widgets; now uses QML to draw everything
|
All done (?) |
