QML and Qt Quick

I am new to Qt framework itself, what I am trying to achieve is I have have customized QGroundcontrol GCS https://github.com/mavlink/qgroundcontrol I want to add firebase support with- Google login Want to get drone live location on fleet management app ( which is using firebase) for which GCSs will be sending data to firebase. I am not sure if Qt InterBase sql plugin will be able to achieve this. Any guidance and help would be greatly appreciated.

@squareroot80 said in How to detect memory leakage ?: qt.qml.gc.statistics From the link: Note: There are memory profiling tools that do not understand this mechanism and over-report JavaScript memory usage. You could be right. This is QML specific and something new for me. Thanks for your post.

I am still using Qt 5 and am trying to adopt the modern approach and move away from context properties - it seemed that this is what we are encouraged to do. However, this issue with qmlRegisterSingletonInstance does not appear to have been explained in the Qt 5 documentation. Having tried to do the right thing, it appears that I am now faced with new complications that are emerging out of the woodwork. If we shouldn't use qmlRegisterSingletonInstance, how are we supposed to provide the dependencies needed by the C++ object? That is, if I want to expose a C++ object as a QML singleton, and it doesn't make sense to default construct that object, what is the recommended approach?

@dheerendra import QtQuick 2.15 import QtQuick.Controls 2.15 TextEdit { id: textedit width: 600 height: 300 textFormat: TextEdit.MarkdownText Shortcut { sequence: "Ctrl+=" onActivated: { textedit.font.pixelSize += 1 } } text: "*Italic* **Bold** # Heading 1 ## Heading 2 body `code block` [Link](http://a.com) " } Maybe you meant to replace "`" with "```". The size of the code block did not increase.

Hi and welcome to devnet, Which version of Qt are you using ?

May be you missed creating the someSqlModel object itself ? Is someSqlModel local object ?

@nenchev then you implement it differently. My suggestion is not a solution applicable to all circonstances as there are no such things. If your validation takes that long to process then you have to give your user a better feedback to let them know longer processing is required and ongoing but it also does not makes sens to add a progress bar if your validation takes less than a second.

Hi there! dear @Leon_2001, As you've said, by setting the Material.background and other properties of Material attached property in the root Item of the application, All the children components, like buttons and other controls, should use the same background color. but this does not work and I have to set the Material.background for each Item that I am using in my application. I could not find out what causes this to happen while in the documents, it is stated that by setting the background for the root Item, it propagates for all children items. could you clarify this for me?

OK, it seems you have to delay the positionViewAtRow call until the model data is loaded. Timer { id: positionTimer interval: 100 running: false repeat: true onTriggered: { if (dataModel.rowCount > 0) { tableView.positionViewAtRow(dataModel.rowCount - 1, TableView.Contain, 0, Qt.rect(0, 0, 0, 0)); running = false; } } } And activate it. TableView { id: tableView model: dataModel Component.onCompleted: positionTimer.running = true }

Maybe you could use QQuickRenderControl.

at least this works fine with QtVKB on Windows + Qt 6.7 import QtQuick import QtQuick.Controls Window { width: 640 height: 480 visible: true title: qsTr("Hello World") Popup { id: popup y: 100 modal: true focus: true TextField { } } Button { text: "open" onClicked: popup.open() } }

@sierdzio After completing the quick project, I added "WinQt.exe" to the system path, Then cmd executes "windeployqt F:\Qt_project\untitled3\Analyse\Analyse.exe --qmldir F:\Qt_project\untitled3\content"; In order to prevent missing DLLS, I will copy all the DLLS under "D:\QT\6.8.0\llvm-mingw_64\bin", but double-click exe still can not run, cmd no output

I think the issue is that you expect to be using the order property you have defined in your Loader but you have also declared an uninitialised order property in your Component which will hide the order defined in the Loader. If you didn't have the order property in your Component, you would simply be able to refer to order (not innerPane.order) as it would be inherited from the context provided by Loader.

FWIW, I'm on Windows 11 and I used to get those warnings. Installing the Vulkan SDK eliminated them.

did you find the solution to this? I'm facing the same problem

Update: Changing Flickable to ScrollView solved the issue. But still it's unclear why this behavior happens with Flickable