replacing dialog with "regular" display

[fcarney]

"accepted" looks like a signal in start_now_or_later.qml.
Is that what you are asking?

[mzimmers]

@fcarney not exactly. Accepted() is a signal provided by the QML Dialog type:

QML Dialog accepted()

I'm wondering:

1. what the non-dialog equivalent to this is, and
2. if I should even be bothering with signals/slots if I'm going to eliminate the dialog.

Thanks...

[fcarney]

Then what is in start_now_or_later.qml?

I create some of my own "dialogs" based upon Window. I use similar signals to control the lifetime of the Window.

[mzimmers]

@fcarney start_now_or_later.qml currently contains the definition of the dialog that I want to replace. If I change the Dialog to Rectangle, and try to run it without further changes, I get a warning at the accepted.connect:

[QT-warning][v-c6ae7a2][thr:12986]qrc:/qml/DelayedStart.qml(18): qrc:/qml/DelayedStart.qml:18: TypeError: Cannot call method 'connect' of undefined

Which makes sense, because I'm not supplying anything to signal a button push (I think). I need to know how to connect these buttons, now that they're not part of a Dialog.

[fcarney]

Rectangle {
  id: rect
  signal accepted() // or put a param in there if required

  Button {
    onTriggered: {
      rect.accepted()
    }
  }
}

[mzimmers]

@fcarney thanks for that. Currently, when the app runs, I get a warning:

unknown(0): QQmlComponent: Component is not ready

According to some other threads, this suggests the application can't find a file, but this used to work. Is there another cause of this warning?

Thanks...

[fcarney]

@mzimmers said in replacing dialog with "regular" display:

createComponent

https://doc.qt.io/qt-5/qtqml-javascript-dynamicobjectcreation.html#creating-a-component-dynamically

Look at the function in that section called: createSpriteObjects. It shows how to delay createObject call if component is not ready.

[mzimmers]

@fcarney interesting. Here's the code that you mentioned:

var component;
var sprite;

function createSpriteObjects() {
    component = Qt.createComponent("Sprite.qml");
    if (component.status == Component.Ready)
        finishCreation();
    else
        component.statusChanged.connect(finishCreation);
}

function finishCreation() {
    if (component.status == Component.Ready) {
        sprite = component.createObject(appWindow, {x: 100, y: 100});
        if (sprite == null) {
            // Error Handling
            console.log("Error creating object");
        }
    } else if (component.status == Component.Error) {
        // Error Handling
        console.log("Error loading component:", component.errorString());
    }
}

This explains a lot, but I don't see the delay that you mention...or was I supposed to add that myself?

This is beginning to add up for me...thanks for the help.

[fcarney]

@mzimmers If component is not ready it connect it to a signal. This delays the execution of createObject to when it is actually ready.

[mzimmers]

@fcarney so, how should I "gate" the processing of the rest of the code:

    nowOrLater.accepted.connect(function () {
    if (nowOrLater.getStartNow()) {
    ...

I could put it in my finishCreation() function, but that doesn't seem quite right.