@probiner
Wrong, you will be able to use QSortFilterProxyModel against QStandardItemModel. What I pointed out was: QSortFilterProxyModel::setSourceModel(QAbstractItemModel *sourceModel) means that it can act as a proxy on any QAbstractItemModel. The docs tell you that QStandardItemModel inherits QAbstractItemModel. Therefore QSFPM can accept QSIM as its source model. And if it some point you derive your own model class from QAbstractItemModel the proxy will work against that for the same reason. This is what inheritance means in C++ and in Python.

Hi again loopless, sorry for getting back to you so late. I'm actually struggling myself to build PySide 2 on Windows (running into different problems, though) so trying to reproduce this has been challenging.

In the meantime, may I suggest that you

a) try with a newer Qt version like 5.15.10
b) try with a newer Python version like Python 3.10

and see what happens?

@SGaist i did, it runs smooth with one camera, since its using available picture to stream, problem is when we have more than one camera, i cant choose each stream directly to communicate with in Qt.
lets say i have a class in python that each def() does one job with a camera, one for focusing on for taking a picture one for sending too AI model and so on, i need to make 6 different object from this class for 6 different cameras and connect them to buttons in Qml, what i explained is alright, but the only part i can not do is the live stream for each camera separately, there is no function or at least i couldn't find which define separate stream of images for separate windows in qml, there are two method so far which looks for available stream of image not a specific one, one is imageprovider, other is paintclass
this is were i have the main problem

Hi and welcome to devnet,

You do not have a constructor without argument.

OK, after more searching I found this answer form the same helpful author.

He says that when the qml files aren't in the root folder you should add
import "qrc:/QML in the main file so it could see other components in the qrc file. (This path is specfic to my case because my qml files are in ./qml folder.)

On thing to note that might seem obvious but I spent quite a few tries to figure it out is that you must compile the qrc file
to py after every change you make to the qml files.

Meaning running pyside2-rcc qml.qrc -o qml_rc.py. Otherwise the imports won't update, and you'll be stuck trying to figure out why the changes you're making don't affect anything.

@SGaist ok merci :)

So the one that creates a file is working but the one that changes a GUI element freezes ? Do I get you correctly ?

@CristianMaureira please find link to my plotting code link .

@JonB Thank you for this, it helped me solve my issues!

This is a different issue that should have it's own thread as it's not related to the problem at hand.

You should also mark this thread as solved.

@CristianMaureira @JonB

Sorry...

I mean

42941a4f-1ef9-4e18-8363-f93753759167-image.png

@JonB argh! I spend a whole day yesterday to figure out how to make it work, and all I needed to do is to write mySignal=Signal() not in the init, but in the class body! Jeeeez.
Thanks a lot! Your advices and link helped!

@Dariusz Filters are flags so if you want to get directories and not dotanddots then use:

it = QDirIterator( dirPath, QDir.Dirs | QDir.NoDotAndDotDot, flags=QDirIterator.Subdirectories )

If you want files:

it = QDirIterator( dirPath, QDir.Files | QDir.NoDotAndDotDot, flags=QDirIterator.Subdirectories )

Same:

it = QDirIterator( dirPath, ["*.exr"], filters=QDir.Files | QDir.NoDotAndDotDot, flags=QDirIterator.NoIteratorFlags )

Okay thanks, I will try it

Thanks @SGaist! I just got a solution on StackOverflow, so I’m marking this as solved, but it’s always great to see how the pros do it, so I’m definitely reading about KExtraColumnsProxyModel too 😊

Hey @ndias,
I am trying to attach to a QQuickWindow.
After some more try & error I finally managed to get it working by using createWithInitialProperties like so:

initialProperties = {"parent": window.contentItem()} object = component.createWithInitialProperties(initialProperties, engine.rootContext())

@JonB
Yeah,I abandoned the monkey patching thing. It's not a good way to edit widgets.
I'll follow your promote solution.I'll try google it.I didn't even know there is a promote feature before.
I'm not a native english speaker,hope my codes and typos didn't make you angry.

Really appreciate the help of yours.Thanks alot.

You should try to comment on the GItHub issue to see if you can get more details of how it was done ?