QML and Qt Quick

@JoeCFD said in Controls.Button do not underline accelerator key: Which OS? And Qt version? Operating System: Manjaro Linux KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.15.65-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i9-12900H Memory: 15,4 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: HUAWEI Product Name: CREF-XX System Version: M1010

UP! Has anyone managed to solve this problem?

I finally got it working. I am not sure what made things start working but here is what I now have. I can now instantiate DataProcess in my main.qml and it will respond to signals from main.qml and do it's thing. Project root (directory) CMakeLists.txt main.qml main.cpp importdata (directory) CMakeLists.txt DataProcess.qml importdata.h import data.cpp The main CMakeLists.txt has the following added. add_subdirectory(importdata) target_link_libraries(FlightLogbook PRIVATE import_moduleplugin) The importdata CMakeLists.txt is # CMakeLists.txt to build import backend. qt_add_library(import_module STATIC) qt6_add_qml_module(import_module URI importdata VERSION 1.0 QML_FILES DataProcess.qml SOURCES importdata.h importdata.cpp ) in main.cpp I added these items. #include <QtQml/QQmlExtensionPlugin> // Plugins Q_IMPORT_QML_PLUGIN(importdataPlugin) before the int main(...) In main.qml I could then do import importdata and in the body DataProcess { id: someid }

@fcarney It's the simple things that get you. So the signal name starts with a lower case letter (I got dinged for that by QML) but when I use it I must make it upper case for the signal's first letter! Arghh. I reworked my testing project based on having to instantiate the additional QML files and this time the signal worked but I see that I did type it as an uppercase letter as onTestSignal so it worked. Thank you for pointing that out as I never would have caught it.

You can also call grabToImage on an Item that you manually set to correct size.

Any updates to this bug? I'm experiencing it in 6.4 only in debugger mode when I press F5 which makes it so impossible to debug the application

Just throw in await sleep(1); at the end of your JS code, then.

Hi, and welcome! @saivineeth said in Resolution problem: When i have run the code then the screen is not coming in full screen If you want the window to be fullscreen, call showFullScreen() if i do maximize then it is coming full screen If you want the window to be maximized, call showMaximized()

The import versions have nothing to do with it. Are you using QRC to embed your .qml files? Do both file are included in the QRC? At the same path?

In QML, i'm using ScrollView along the TextArea to view the input commands and output. I'm facing two problems here: The TextArea doesn't scroll down automatically, i want the ScrollView to show me the latest output so that i doesn't have to scroll down manually to see it. I'm unable to change the TextArea background color. The background I want to be transparent so that it reflects the main windows background. ScrollView { id: view anchors.fill: parent TextArea { id: outputTxt color: "black" readOnly: true selectByMouse: true text: "TextArea\n...\n...\n...\n...\n...\n...\n...\n...\n...\n...\n...\n...\n...\n...\n...\n...\n...\n...\n...\n...\n" anchors.fill: parent } } [image: 3e7e8086-937b-4d31-810f-b2b80d4d683b.PNG]

Restarting the target Device worked for me. However, to delete any previously installed Application, delete it via XCode and not manually from the device {Delete App} and then restart. If already deleted manually, simply restart the target device. Tested on Qt 5.15.9 and iPad 6th gen and OS 14.0

I meant Q_DECLARE_METATYPE(application::BookOperationStatus) but it probably does not apply in this case.

Create at least two qrc files: one for images and one for qml. Better not to mix them up.