Connections with two targets?

[tekojo]

Hi @SafaAlfulaij

Yes, just connect the signals and slots one by one as you need.

There is even a class for doing more complicated connection mappings:
http://doc.qt.io/qt-5/qsignalmapper.html

[SafaAlfulaij]

@tekojo I was talking about QML Connections type :)

[tekojo]

Ah, sorry I misunderstood.

But the same answer :)
Connections can be used to connect multiple signals to one slot
http://doc.qt.io/qt-5/qml-qtqml-connections.html#details

[SafaAlfulaij]

@tekojo Sorry, but I couldn't understand how.

Is it like (This is just an example):

MouseArea {
    Connections {
        onClicked, onEntered: foo(parameters)
    }
}

And Do I use:

target: button, textInput

I can make two Connections types, but that's not the question.

[p3c0]

AFAIK there is no way to do this in Connections. An alternative is to use the connect method.

[p3c0]

@SafaAlfulaij Not exactly a solution but try the following:

Item {
    width: 100
    height: 100

    QtObject {
        id: sender
        signal post (var obj, var data)
    }

    Item {
        id: a
        objectName: "ItemA"
        Component.onCompleted: {
            sender.post(this, "This is from Item A")
        }
    }

    Item {
        id: b
        objectName: "ItemB"
        Component.onCompleted: {
            sender.post(this, "This is from Item B")
        }
    }

    Connections {
        target: sender
        onPost: {
            console.log(obj, data)
            console.log(obj.objectName)
        }
    }
}

In onPost you get access to individual objects.

[kshegunov]

Is the Connections component a singleton or am I missing something again? As far as I can tell it's a regular QObject, so I think this should work:

MouseArea {
    // ...
    Connections {
        target: button
        onClicked: foo(parameters)
    }
    Connections {
         target: textInput
         onEntered: foo(parameters)
    }
}

[p3c0]

@kshegunov that is possible too. But OP is asking for a single Connections objects and which can accept 2 targets.

[kshegunov]

@p3c0
Well, that's only marginally less verbose. And since onClicked, onEntered etc. are already slots I don't see how that feature should work in the first place ...

[p3c0]

@kshegunov Perhaps OP must have thought of comparing c++ feature