Did you ever get anywhere with this approach? On Wednesday, June 10, 2015 at 6:26:57 PM UTC-4, Russell Warren wrote: > > Has anybody tried getting pyqtgraph working in a Qt Quick 2.x application? > > With Qt Quick 2 being OpenGL and scenegraph only (no QGraphicsView) I > figured pyqtgraph was pretty much a non-option. However, I've just seen > that there is a QPainter API available: > > http://doc.qt.io/qt-5/qquickpainteditem.html > > This makes me think it may be feasible with a bit of elbow grease. That > API draws indirectly and seems like it needs to upload the full image to > the GPU on every update, so I don't know how fast that would be. I also > certainly don't know enough about OpenGL to know where all of the rendering > happens in the first place, or what gets shipped where, how, and with what > bandwidth... but it looks promising, anyway! Maybe it makes more sense to > wait for Vispy to be usable and try and pipe that to Qt's OpenGL context > somehow? > > There's obviously a heck of a lot more to pyqtgraph than the graphics > rendering (I recall that the mouse interaction code is pretty beefy), but > has anybody tinkered with this yet? > > With Qt Quick Components [1] getting better over time (5.5 even has a > treeview coming [2]), I'm definitely curious to start working in QML. > > Russ > > [1]: http://doc.qt.io/qt-5/qtquickcontrols-overview.html > [2]: https://wiki.qt.io/New_Features_in_Qt_5.5 > > >
-- You received this message because you are subscribed to the Google Groups "pyqtgraph" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/pyqtgraph/9c3a0111-6c26-4940-8e37-dc61a3314c64%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
