QML and Qt Quick

@Fan__ said in PathView delegate use attached attributes: QtVersion: 5.12.5 QtVersion: 5.12.5 is too old. Upgrade Qt above 5.15 or 6.8.

The sizeHint of a QQuickWidget is based on the actual size of it's root item and not on its implicit size, I think that explains the discrepancy. minimumSizeHint() or minimumSize() are not implemented for QQuickWidget but they are for QLabel. You could try inheriting from QQuickWidget and override both sizeHint and minimumSizeHint by returning its root QQuickItem's implicit width/height.

Qt 6 changed some input event handling, so you might need to adjust the event capturing logic. So the solution is: GridView { id: gridViewNodes anchors.fill: parent cellWidth: 140 cellHeight: 120 clip: true highlightMoveDuration: 100 reuseItems: true // unselect MouseArea { anchors.fill: parent propagateComposedEvents: true onClicked: (mouse) => { gridViewNodes.currentIndex = -1 nodeListMultiSelectionHandler.resetSelection() mouse.accepted = false // allow selection } }

The issue was solved Add child model in parent repeater's Compoenet.onCompleted. Repeater { id: repeater1 model: backend.graphModel Component.onCompleted: { repeater2.model = model.GraphMaximumCount } } Repeater { id: repeater2 }

you need to call setFlag(ItemAcceptsInputMethod, true);

I think this repository can help you. https://github.com/tlaemmlein/TableViewQtQuick2Examples

@GrecKo Ah, cool, thank you!

@GrecKo thanks ,i will try video output later, now i use QQuickFramebufferObject.

That's something worth discussing. I currently don't know the details of the Wayland protocols and how to leverage them from Qt for your situation.

Hi, Which version of PySide6 would that be ? Which version of Nuitka ? On which OS ? Also, while the logs nuitka might mention webengine, are you sure it's actually included ? I did a test on macOS and ended up with a 84MB binary which is not that surprising accounting for the QtQuick stuff plus QtCore and QtGui.

I don't understand why something so essential is such a mystery. The documentation page presents a sample fise: [code] <RCC> <qresource prefix="/"> <file>images/copy.png</file> <file>images/cut.png</file> <file>images/new.png</file> <file>images/open.png</file> <file>images/paste.png</file> <file>images/save.png</file> </qresource> </RCC> [/code] It then proceeds to say, one would assume with reference to the above: The Qt Resource System The Qt resource system is a platform-independent mechanism for shipping resource files in an application. Use it if your application always needs a certain set of files (like icons, translation files, images), and you don't want to use system-specific means to package and locate these resources. Most commonly, the resource files are embedded into your application executable, or in libraries and plugins that are loaded by the application executable. Alternatively, the resource files can also be stored in an external resource file. The resource system is based on tight cooperation between Qt's rcc resource compiler, the build system, and the Qt runtime API. Note: Currently, the Qt resource system does not make use of any system-specific capabilities for handling resources, such as the ones on Windows, macOS, and iOS. This might change in a future Qt release. The Qt Resource Compiler (rcc) The Resource Compiler (rcc) command line tool reads resource files and generates either a C++ or Python source file, or an .rcc file. The list of files and related metadata is passed to rcc in the form of a Qt Resource Collection File. By default, rcc will generate C++ source code that is then compiled as part of an executable or library. The -g python option generates Python source code instead. The -binary option generates a binary archive that is by convention saved in an .rcc file and can be loaded at runtime. Note: While it is possible to run rcc from the command line, this is typically best left to a build system. See also the sections about qmake and CMake below. Qt Resource Collection File (.qrc) A .qrc file is an XML document that enumerates local files to be included as runtime resources. It serves as input to rcc. Here's an example .qrc file: <RCC> <qresource prefix="/"> <file>images/copy.png</file> <file>images/cut.png</file> <file>images/new.png</file> <file>images/open.png</file> <file>images/paste.png</file> <file>images/save.png</file> </qresource> </RCC> Each <file> element in the XML identifies a file in the application's source tree. The path is resolved relative to the directory containing the .qrc file. [quote] The path is also used by default to identify the file's content at runtime. That is, the file titlebarLeft.png will be available in the resource system as :/res/titlebarLeft.png or qrc:/res/titlebarLeft.png. To override this default run-time name, see Prefixes and Aliases. [/quote] titlebarLeft.png is not in the file example, I know it's nitpicky but it does not instill confidence. Further it is not made clear which instructions are being given for the QT creator IDE where one would assume that lots of setup is done for you, that is the point of an IDE as well as presumably for use of the library on it's own in whatever environment the programmer chooses.

Hey @eternal_void , I just got back to using Qt for another project. This is new account (I was @talksik), but here are my findings in a similar post after a ton of research and coming up with a custom solution not really mentioned anywhere: https://forum.qt.io/post/821291

This has been a question of mine for over a year. I resorted to having a factory class that has methods to instantiate various view models (and pass in dependencies) and return the pointer to that view model. This factory would be exposed to QML via singleton or contextProperty at the start of my program. Any QML view can decide which view models it wants and doesn't deal with dependency injection. Here is an example: class ViewModelFactory : public QObject { Q_OBJECT QML_ELEMENT QML_SINGLETON public: Q_INVOKABLE HomeViewModel* createHomeViewModel(QObject* parent = nullptr) { // Inject dependencies from ApplicationModels auto& appModels = ApplicationModels::instance(); return new HomeViewModel(appModels.smartHomeService(), appModels.userService(), parent); } }; Now, the above example makes ApplicationModels a singleton and passes it to the view model, but you could imagine a world where the factory can manage the dependencies without them being singletons. It took a lot of thinking and I gathered this approach by looking at how QtWidgets does things: a very hierarchical object structure where the MainWindow class would contain everything within it and proctor instantiation, DI, and more. QML just has access to what is publicly exposed by the ApplicationModel/factory, and no longer needs access to dependencies for ViewModels to use their desired view model. Note: I have not tested this yet (my fear being that I do NOT know the impact of calling factory methods on init of a Qml component)

The error you're encountering ("QML Image: SSL handshake failed") typically happens when there's a problem establishing a secure connection between the QML application and the server you're trying to connect to. This is often caused by issues with SSL certificates, the server's configuration, or network problems. To resolve this error, you can try the following steps: Check SSL/TLS Configuration: Ensure that the server you're connecting to has a valid SSL certificate. If you're using a self-signed certificate, it may not be trusted by the system. Make sure the certificate is correctly installed. Update QML/Qt and SSL Libraries: Sometimes, outdated libraries can cause compatibility issues. Make sure you're using the latest version of QML, Qt, and SSL libraries (OpenSSL). Verify Network and Proxy Settings: If you're behind a proxy or firewall, ensure the settings are properly configured and not blocking the SSL handshake. Trust Certificates: If the certificate isn't recognized by the system, you may need to manually add the certificate to the trust store. Enable Debugging: You can enable debugging in Qt to get more information about the SSL handshake failure. Set the following environment variable before running your application: ini Copy Edit QT_DEBUG_PLUGINS=1 For more detailed information and troubleshooting, you can refer to the following resources: Qt SSL documentation OpenSSL documentation Common SSL handshake errors Let me know if you need more help!

Ah, didn't read this. Thanks for the hint...