When to use .qml and when to use .ui.qml ?
-
Hi
I'm new to Qt Quick/QML and struggling to understand when I should be using a straight QML file and when to use the Qt Quick UI File option.
I've watched various videos and some developers seem to use a UI File when developing a reusable component and others use a plain .qml when adding a form/view.
These almost seem interchangeable, in fact the UI File option just seems to append 'Form' to the name and use the .qml file almost like a header.
Are there any advantages/disadvantages of using either in certain situations (e.g. creating a reusable component or adding a form/page to an app) ?
Also, is there a 'best practice' to help decide which to use ?
Thanks in advance
Alan
-
They can be used identically. The .ui. in the name just affects how Qt Creator will treat the file. It opens .ui. files in the designer instead of the text editor by default. At least that is how I understand them.
Edit:
As for "best practices" I am not sure what that would be. -
Hi
I'm new to Qt Quick/QML and struggling to understand when I should be using a straight QML file and when to use the Qt Quick UI File option.
I've watched various videos and some developers seem to use a UI File when developing a reusable component and others use a plain .qml when adding a form/view.
These almost seem interchangeable, in fact the UI File option just seems to append 'Form' to the name and use the .qml file almost like a header.
Are there any advantages/disadvantages of using either in certain situations (e.g. creating a reusable component or adding a form/page to an app) ?
Also, is there a 'best practice' to help decide which to use ?
Thanks in advance
Alan
@Alan-B
In the end it's totally up to you, use what gives you the most overview, or that what you have the most mastery over.I personally have, in my 3 years of active QML usage never used a single
.ui.qmlfile nor a singleQt Quick Layoutanchors and x/y bindings for life 🤘
