QML and Qt Quick

I hadn't noticed the addition of the component keyword. Thanks for pointing it out. The syntax I've used previously is: Item { property Component myComponent: Text { ... } Component.onComplete: myComponent.createObject() }

The idea behind the dynamic backend is to be able to detect what is available. From the looks of it there's an issue with the driver on that machine. In any case, forcing the backend to desktop for all Qt applications on a system is wrong. It should be done on an application basis.

@Circuits you can access the current window from "anywhere" using the attached property. Is thats what you are after?

@J-Hilk That solved the error. Thank you :)

@ACaldas If they're all visual children of a container item, this imperative block works: onToggled: { for (var child in parentItem.children) { if (undefined !== parentItem.children[child].checked) { parentItem.children[child].checked = false; } else if (undefined !== parentItem.children[child].enabled) { parentItem.children[child].enabled = false; parentItem.children[child].value = 0; } } } You might also look into either directly binding the values, or using a State. I don't think that these will result in fewer lines, but the relationships might be easier to understand and modify when necessary.

@Silvia-V said in Component load modelData failed: @jeremy_k Well, The mechanism make me confused Fond a way to fix it ... If there is no better solution, it can only become solved. If that works and is something you find understandable, that looks like a reasonable structure. Presuming that this is representative of the real structure rather than a compact example, you might consider changing property Component delegate to be an alias for the Repeater delegate, and then define the default delegate inline. For non-inline delegates, I favor passing modelData as an explicit property. That makes the delegate easier to reuse or test outside of a view. Thank you @jeremy_k Forgive my broken English[cry] The question was clear, and the included code resolved any doubt. There's nothing to apologize for.

@J-Hilk Dimming effect is not related to background. I think I need to use Overlay.modal attached property like so: Popup { ... modal: true Overlay.modal: Rectangle { color: "#aacfdbe7" // color/opacity } }

@fcarney actually, I am not too bothered about anchors and centering as the popups are initially shown in positions based on user mouse clicks, etc. The initial stumbling block for me was just getting hold of the top-level window size and being notified of changes. Now that I can do that, I can think about the details of how I need to react to the changes.

You should not want that. Delegates are only a visual representation of the model, and ListView is designed to only show (and instantiate) what the user needs to see. Forcing it to show everything will decrease performance. If you definitely need to generate UI for all elements in a model, use Repeater.

Rectangle { anchors.fill: parent } This will make your Rectangle fill the window.

I did what you said, there was one thing that I had to change that you would have overlooked, but this loads the tile = 0 for all tiles.

@Puya said in How to apply the same background to all DelegateChioces in DelegateChooser?: How would that work with the delegate (a QML component) coming from the model (C++ object)? No idea. I don't know what that means.

I suspect that adding a scrollbar to a scrollview disconnects it from everything. I've read the docs, and although the don't explicitly say so, I think scrollView contains an inherint scrollbar. So add a new one: ScrollBar.vertical: ScrollBar {} cases a standlone scrollbar connected to nothing.

@Gunkut i think you are better off by using a StackView element instead of a loader. To push (a new page) into or pop (remove the current page) the StackView in which your current page/window currently is use the provided attached properties (e.g. StackView.view.push() / StackView.view.pop())

@KroMignon Thank you, it works

I'm seeing the same thing here as well. Has anyone reported it as bug?

Seems like I have to write event.accepted = false and then it works