As I said before, when you show us these screenshots we need to see the code file being compiled open in the main pane, so that we can see what you have written. You need to do that every time you want to ask a question about your code!
@Hronom: Did you try it with QtAudio3d? I don't want to use it, I am only interested, if it works
@Thomas Zander: QML doesn't have really much opertunities as in Qt4. And if it's not easy to do it in QML, it will never work in QML, which means, that QML is a language with limits, but you can implement very fast simple widgets. That's the reason, why I prefer C++. I will learn QML, when I got time for that, but now, I only developping complex desktop applications for Linux, Windows and Mac and need their styles.
What using a custom build of Qt: always use the full path to qmake. You may have the one provided by your distribution installed which will be the one invoked. One other thing you did not take into account is unless you are doing a developer build (because you want to hack on Qt) you have to call 'make install' as last step.
If the data contained in the model is all of basic types or implicitly shared types then it's possible to already use the current framework without ever triggering any expensive* copy
, to point 2:
There's no clarity on how to support different types in different roles
would we need an additional template argument for each used role beyond Qt::UserRole? is so the problems above grow exponentially with the roles
And to point 3:
No possible implementation for a reliable dataChanged emission if model internals are exposed directly
*expensive = a copy that implies more that a:
memcpy of less than 65bits and
an increase/decrease of a numeric reference counter
Hallo jungs und mädels, frohe Weihnachten!!
Ich beschäftige mich grad mit dem modell view konzept um eins meiner Projekte zu realisieren!
Ich hab euer Tutorial gefunden und wollte es durcharbeiten! Aber leider sind alle links zu den dateien und des tutorials tot. Könntet ihr das tutorial vllt wieder auffrischen?
Das wäre sehr hilfreich für mich!!
Bluntly speaking, your MyMplCanvas __init__ implementation is a mess. You are calling the init method of QLabel, do some stuff, then call the base class init implementation through super, set the parent independently, then you manage to use a method called imshow which is also a method from OpenCV's highgui module.
You really should start by cleaning this up.
Do things step by step.
First question is: taking the rubber band part out of the equation for now, why do you need all these modifications on the MplCanvas class ? Are you sure you are using it correctly ?
Nothing wrong, much less "vastly inferior" with Qt containers - their performance is on par with std containers, and Qt containers use is actually less verbose and much easier to use. std containers are overly verbose, pretty much all operations require iterators.
He is right about the pricing though. It needs to be cut at least in half to become reasonable.