QML and Qt Quick

@PrajwalG99 hi and welcome to devnet, Might be a silly question but why not use the Qt 6 version that comes with your distribution ?

adding this code solves the problem for IOS AVAudioSession *session = [AVAudioSession sharedInstance]; NSError *err = nil; [session setCategory:AVAudioSessionCategoryPlayAndRecord withOptions:(AVAudioSessionCategoryOptionDefaultToSpeaker | AVAudioSessionCategoryOptionAllowBluetooth | AVAudioSessionCategoryOptionAllowBluetoothA2DP) error:&err]; [session setMode:AVAudioSessionModeSpokenAudio error:&err]; [session setPreferredSampleRate:48000 error:&err]; [session setPreferredIOBufferDuration:0.01 error:&err]; [session setActive:YES error:&err];

I just tested - it does indeed produce QML console messages. (The output is kind of smashed together, but the content is there.) [image: b7a1823a-dccf-4ead-931f-d2d47df98bf3.png] Thanks for pointing this out, @cristian-adam .

You're welcome! Thank you for sharing your journey and your solution. Here are some additional tidbits that might be of interest to you: Anchor default values Items are always placed at their parent's top-left by default. So, you can omit these lines and still get the same result: anchors.top: parent.top anchors.left: parent.left Having said that, you can also keep them for clarity. Label vs. Text Displaying text inside a coloured rectangle is a very common requirement. You can simplify your code by using Label instead (https://doc.qt.io/qt-6/qml-qtquick-controls-label.html ). Add import QtQuick.Controls.Basic and try the following: Label { id: name background: Rectangle { color: "blue" } text: myContactInfo.name font.pointSize: 30 } Label { id: address anchors.top: name.bottom background: Rectangle { color: "green" } text: myContactInfo.address font.pointSize: 15 } Note: One difference is that Label might change your font colour based on your OS settings (e.g. dark mode) Positioners vs. Anchors See https://doc.qt.io/qt-6/qtquick-positioning-layouts.html -- instead of anchoring your 2nd label to the 1st label, you could put them inside a Column: Column { // Quiz (open-book): What is the width and height of this Column? Label { id: name background: Rectangle { color: "blue" } text: myContactInfo.name font.pointSize: 30 } Label { id: address background: Rectangle { color: "green" } text: myContactInfo.address font.pointSize: 15 } }

@RokeJulianLockhart hi, This thread is 10 years old and was created with the previous version of the forum software where there was no concept yet of "solved state" hence the [solved] in the title which was how threads were marked at that time. [edit: fixed the resolution]

@RokeJulianLockhart said in plugin cannot be loaded for module "QtQuick.Layouts": Cannot protect module QtQuick.Layouts 2 as it was never registered QML debugging is enabled...: qml-qt6 ./main.qml works perfectly Great! Thanks for sharing. Just remember that you are bound to your distro's version of Qt 6, so the qml-qt6 tool won't be able to process QML code that uses functionality from newer versions. The tool is also intended as a way to quickly preview *.qml files. It won't be able to handle custom types/classes defined from C++ or Python for example (unless you put your class in a C++ plugin that's formally installed)

I thought seetings "Breeze" would change QQuickControls aspect but I think I'm wrong. @Jim-Gir, yeah: print( "Current QQuickStyle: ", PySide6.QtQuickControls2.QQuickStyle.name() ) PySide6.QtQuickControls2.QQuickStyle.setStyle("Breeze") print( "Current QQuickStyle: ", PySide6.QtQuickControls2.QQuickStyle.name() ) ...returns "Fusion", then "Breeze", yet the controls appear identical regardless, despite them being quite different styles: Fusion Breeze [image: 441c28d5-597c-45c4-abce-c2b44c341273.png] [image: 057417eb-1519-4126-88fb-290f22823792.png] Perhaps, ask at discuss.kde.org/t/1240, or a new thread on that instance? Environment Operating System: Fedora Linux 42 KDE Plasma Version: 6.4.4 KDE Frameworks Version: 6.17.0 Qt Version: 6.9.1 Kernel Version: 6.15.9-201.fc42.x86_64 (64-bit) Graphics Platform: Wayland

You can simply set iconName to the the name the icon has in the theme and use iconSource as a fallback. Can anyone provide an example for this? I also want to utilise the system icons, if possible.

@KillerSmath, it doesn't for me (versionlessly): [image: 76ffee03-5032-44ac-8fcd-c40f65666fa0.png] If it did, I doubt that stackoverflow.com/questions/45066601 would have been asked (I doubt it's a failure of my compositor).

@JKSH, thank you! That provides a direct answer, of which spacing: fontMetrics.averageCharacterWidth appears to be the most general-purpose solution. I'm surprised that the default spacing value is 0 for so many elements, though. Perhaps, KDE's QQuickStyle lacks defaults that it should provide? Regardless, is this generally how spacing is conducted in QML? If so (which I expect), I'll presume that there's some guidance documented about when/where one should utilise such values?

Hi, and welcome! @Morty56 said in About the position of engine->rootContext()->setContextProperty() and engine->load() resulting SEGFAULT: What I've done is just move one method to another by integrating two functions to resolve this issue. Nothing else has changed. Here is my code. Which part could bring the result of segmentation fault? I am so confused. Your code could contain a race condition, where moving functions around changes the outcome of the race. Check your code using tools like ASan and TSan.

@SanderVc said in Sudden QML system issues not solved by reinstall: qrc:/qt/qml/org/kde/breeze/impl/Theme.qml:10 QtObject is not a type Looks like your project incorporates external KDE types. How do you add them to your project? Please show us your *.pro/CMakeLists.txt file where this happens. For further debugging, set the environment variable, QML_IMPORT_TRACE=1 before launching your app.

@aurora_ns, your thread is inaccessible to me. As post/824859 explains, qmlscene does not support the shebang. At least, not #!/usr/bin/env -S qml. Removing that remediated that error for me (although merely resurfaced post/830428). If the error is prepended with :1, it should for you.

@MohsenNz, ListView appears to inherit from Flickable, which ScrollView appears to extend: ScrollView provides scrolling for user-defined content. It can be used to either replace a Flickable, or to decorate an existing one. As of Qt-6.0, ScrollView automatically clips its contents if you don't use a Flickable as a child. If this is not wanted, you can set your own Flickable as a child, and control the clip property on the Flickable explicitly. Consequently, their usage isn't 1:1. However, I don't understand what their uses are.

@Jkimmy, perhaps follow post/557344. It's a year older, so if anyone does ever respond, it'll be there.

Hi, Are you using a static build of Qt ? If not, did you deploy the corresponding plugin and library along your application ?

[image: b3140f50-9678-499a-8257-7bffe2cbd200.png] [image: 7f4a47e0-cccc-4b09-b11a-20ae23c69ef9.png] If the code within the signal handler is the same, the program can be compiled but it will fail to run and even cannot be debugged.