QML Qt.createQmlObject

[axed]

Why would you use createQmlObject for such thing?

Because the documentation states that this is only one of two options.

src: https://qt-project.org/doc/qt-5-snap...tcreation.html

So Qt.createComponent looks like some overkill when i just want to add some ToolButton.

Did you try splitting your component definition into multiple lines to avoid the semicolon after the import statement?

Why should i? The documentation does the same in it's examples.
https://qt-project.org/doc/qt-5-snap...-string-of-qml

Hard to say without knowing what documentation you mean.

http://doc.qt.io/qt-5/index.html
https://qt-project.org/doc/qt-5-snap...s-toolbar.html

Yes. Use the QML debugger and analyzer that comes with Qt Creator. However your errors are very simple so there is no need to use a debugger to avoid them.

Nice to hear that they are simple, yet i found no reference to what they mean.

[anda_skoa]

So Qt.createComponent looks like some overkill when i just want to add some ToolButton.

I think what wysota meant is: "why don't you just add a ToolButton"?

toolBar: ToolBar {
        RowLayout {
            anchors.fill: parent
 
            ToolButton {
            }
        }
    }

toolBar: ToolBar {
        RowLayout {
            anchors.fill: parent

            ToolButton {
            }
        }
    }

To copy to clipboard, switch view to plain text mode 

Cheers,
_

[axed]

I think what wysota meant is: "why don't you just add a ToolButton"?

As the title may suggest, i want/need to do this at runtime :/

[anda_skoa]

As the title may suggest, i want/need to do this at runtime :/

Maybe it would help to know what exactly you are trying to achieve.

Cheers,
_

[axed]

@QML ToolBar: Binding loop detected for property "implicitWidth""
Something was anchored by me when it shouldn't have been (as some items are automatically anchored). Maybe it was the toolbar - i can't remember right now, but that one sounds right.

This is how i'm creating things at runtime right now:

function createByData(targetQmlSourceCode, parentItem, targetQmlModuleName) {
try {
 
        var component = Qt.createQmlObject(targetQmlSourceCode,
                                               parentItem,
                                               targetQmlModuleName);
        return component;
    }
    catch (error) {
        console.error("There were QML errors:" + JSON.stringify( error.qmlErrors));
    }
 
    return 0;
}

function createByData(targetQmlSourceCode, parentItem, targetQmlModuleName) {
try {

        var component = Qt.createQmlObject(targetQmlSourceCode,
                                               parentItem,
                                               targetQmlModuleName);
        return component;
    }
    catch (error) {
        console.error("There were QML errors:" + JSON.stringify( error.qmlErrors));
    }

    return 0;
}

To copy to clipboard, switch view to plain text mode 

The documentation was a little but fuzzy about details like how to access the "qmlErrors" object and that you have to use try{} and catch(){} blocks for the cases where Qt.createQmlObject would otherwise suicide-bomb the qmlapplicationengine.
Now that my frustration with this problem has faded, i'd like to apologize if i might have sounded a bit harsh.
Thank you guys for your contribution!

[anda_skoa]

It would still be interesting why you need that at all.

Such imperative code is commonly unnecessary, most often there is a way cleaner solution.

Cheers,
_

[axed]

It would still be interesting why you need that at all.

Such imperative code is commonly unnecessary, most often there is a way cleaner solution.

Cheers,
_

I wrote a third-party plugin handler for my application and needed to create the "shortcut-icons" for those plugins at runtime.
Generating a ListModel and throw that into a ListView would also have done the trick i guess, but i prefered actual Buttons to keep up with the design of the application.

[wysota]

I wrote a third-party plugin handler for my application and needed to create the "shortcut-icons" for those plugins at runtime.
Generating a ListModel and throw that into a ListView would also have done the trick i guess, but i prefered actual Buttons to keep up with the design of the application.

You could have declared the list of buttons in the plugin and then pass that list to your handler so that it can put them in the toolbar.

Your current design is a secutiry risk -- you are accepting code from a third-party plugin that you execute on behalf of your object.

[anda_skoa]

I wrote a third-party plugin handler for my application and needed to create the "shortcut-icons" for those plugins at runtime.
Generating a ListModel and throw that into a ListView would also have done the trick i guess, but i prefered actual Buttons to keep up with the design of the application.

Why would having the data in a model keep you from using buttons?

Creating instances of any type based on a model is a standard use case, implemented with the Repeater element.

Cheers,
_

[wysota]

So Qt.createComponent looks like some overkill when i just want to add some Tool Button.

I think createQmlObject is a larger overkill but anyway I didn't mean to use createComponent. You can declare a component inline in the original QML document and just instantiate it when needed. See the docs on Component element.

By the way, the title doesn't suggest you want to do anything dynamically.