8 August 2021
bayangtext not yet in the index
Oh seems like you may not have seen @QmlElement in use. Super easy now - you can register the python type with QML and just do:
Worker {
id: worker
forecastSource: "forecast.json"
}
And then elsewhere in your QML refer to worker.forecast, presuming you set up your Worker class with forecastSource and forecast Properties.
Ricardotext not yet in the index
? Not sure what your question is?
The idea is for nurses to dump a bottle of pills onto a surface above which is an RPi webcam that takes a photo of the surface, feeds into my logic, and displays a result of how many pills it finds.
Keith KyzivatI think we have some examples that show this, but if we don't, I can make one.
I prefer use slot, I have other function which are doing heavy processing like get data from api.dClimate.net, and then use pandas to sort value and get specific value.
Going slightly back to the QML imports topic: it is indeed a not very clear system. For example, currently I have several QML files with different widgets but they still communicates through the global id properties. Hence, these modules are not truly isolated, such approach just helps not to overflow file with thousands lines of code but doesn't completely separate the code. I don’t fully understand how one file can reach another one trough a such mechanics. JS or Python import system seems more logical than QML one to me. Though, this still can be like this due to my lack of knowledge/biases to other languages and it is an off-topic for this chat, anyway.
In two words, what are the main issues preventing the implementation of packaging pipeline? For QML apps. I mean, I remember several years ago I've successfully bundled PyQt5 app (with some graphical assets) via Pyinstaller. I see some worries in this chat from time to time regarding the packaging, what are those particular drawbacks everyone talking about? Is something totally different in the PySide world?
usserrGoing slightly back to the QML imports topic: it is indeed a not very clear system. For example, currently I have several QML files with different widgets but they still communicates through the global id properties. Hence, these modules are not truly isolated, such approach just helps not to overfl
ids are local to a QML file, but properties are not.
usserrGoing slightly back to the QML imports topic: it is indeed a not very clear system. For example, currently I have several QML files with different widgets but they still communicates through the global id properties. Hence, these modules are not truly isolated, such approach just helps not to overfl
Not quite off topic - I'd say QML is in the scope of discussion here.
usserrIn two words, what are the main issues preventing the implementation of packaging pipeline? For QML apps. I mean, I remember several years ago I've successfully bundled PyQt5 app (with some graphical assets) via Pyinstaller. I see some worries in this chat from time to time regarding the packaging,
I don't think it's any different. It's all about getting it packaged in a way that the binary assets work properly, plugin libs are findable once running, etc. Should be the same issues you'd have with PyQt
Ссылка
click to show
click to show
Welcome Ksalsjxnxdj 🎉 🎊
Verify you are not a bot solving the captcha!
Remember to check the documentation page https://doc.qt.io/qtforpython/ and the wiki https://pyside.org if you have some questions.