QML and Qt Quick

Hi and welcome to devnet, From a quick search, QtQuick WebGL is not available at all in Qt 6 currently. See here for the comparison and explanation. Depending on what you are developing, Qt for WebAssembly might be a possibility.

I should point out, that you could use a push instead of a replace. Then have a back button that pops the last one off to go back. So you could use it the same way except with depth instead of how I did it.

This doesn't seem to be implemented. Setting Qt::Popup doesn't work for QQuickView, and doesn't work for QQuickWidget, either. A workaround is to use a plain QWidget as popup, and add a QQuickWidget as child.

@jsulm Ok I didn't understand what this sentence actually says. Thanks for pointing out!

@GrecKo I was trying to find a way to execute an animation without declaring it separately. In "meta-code": onSignalTrigger: { timer.stop() doSomething() doSomethingElse() // animate property PropertyAnimation { target: theObject; property: "opacity"; to: 0 } } The long way is: PropertyAnimation { id: myAnim; target: theObject; property: "opacity"; to: 0 } onSignalTrigger: { timer.stop() doSomething() doSomethingElse() // animate property myAnim.start() } I find the first syntax is more readable

@J-Hilk - sorry, scrap that last comment, I changed it to value and now it works!, yay!!, thank you @J-Hilk, you sir are a genius!! :)

Code looks fine (but when posting on forum, please wrap it with ``` tags). Run it with a debugger, or with address sanitizer, and see where it really crashes. Perhaps you do something wrong in main.cpp?

@fcarney yeah, probably would have to just test and measure the performance, which is probably quite a bit of work with unsure result and sadly, I don't have unlimited time.. Meanwhile, I've came up with different approach and even tested it a little and it seems to be working. Not sure how viable it is or what pitfalls it might have though. Basically, I'd change my models into models of QObjects with Q_PROPERTY for every role. Model would function as normal but would have extra functionality - it would be possible to register another QObject of same class as a mirror (each xChanged property signal from source item would be connected to setX signal of the mirror). This mirror QObject would exist in QML and its properties could be used in the same way as model roles. Repeater { model: playerModel delegate: Item { Label { text: "Player name: " + nameRole } PlaylistMirror { id: playlist uuid: playlistUuidRole } Label { text: "Playlist name: " + playlist.name } } This mirror object would register itself to the model whenever its uuid property changed. Something like this (with checks ofc): void register(QUuid uuid, Playlist *mirror) { Playlist * source = find(uuid); connect(source, &Playlist::nameChanged, mirror, &Playlist::setName); mirror->setName(source->name()); // initial sync // same for all roles } It should be safe - if the source object got destroyed by mistake, it would simply stop updating the mirror instead of crashing that would happen if I just got raw pointer from the model. There would have to be some logic for cleaning (if mirror changed the uuid, it would have to disconnect and connect again; if source was deleted, mirror should be cleaned) but otherwise, it seems like decent solution. The performance hit of generating xChanged signals without any receiver should be negligible and there is no need for any extra models or filtering. Higher memory usage is non-issue. Here's diagram for better illustration: [image: 7384b685-a006-435b-be61-fa8afecc899d.png] What do you think?

You can use the fact that the popup's contentItem of the ComboBox is a ListView and use ScrollBar vertical attached property: Binding { target: comboBox.popup.contentItem.ScrollBar property: "vertical" value: ScrollBar { policy: ScrollBar.AlwaysOn } }

Thanks, I will try it.

on Linux (GStreamer backend) , usually udp should be used to playback the stream