> On 25 Sep 2017, at 09:28, Daniel d'Andrada wrote:
>
> Hi All,
>
> I wanna have the following (A):
>
> Foo {
>Button {}
> }
>
> or (B):
>
> Item {
>Button {}
>Foo {}
> }
>
> Where "Foo" is an item that is interested only in drag gestures. So when
> one is performed it does its
Actually MouseArea.drag.filterChildren is just what I was looking for
(so you can implement option A in pure QML). Sorry for the noise.
- Daniel
On 09/25/2017 09:58 AM, Andrew Ialacci wrote:
I think you can chain the signal calls using signal.connect(otherSignal) and
then set the drag target
I think you can chain the signal calls using signal.connect(otherSignal) and
then set the drag target to null.
I had to implement something like this while writing an MDI windowing system.
Admittedly though I did resort to moving 99% of the geometry manipulation and
event handling to CPP.
I w
Hi All,
I wanna have the following (A):
Foo {
Button {}
}
or (B):
Item {
Button {}
Foo {}
}
Where "Foo" is an item that is interested only in drag gestures. So when
one is performed it does its thing. It ignores clicks, letting them go
to the Button element inside/behind it.
So A
