I want to stop stealing MouseSignal of Flickable



  • I have asked the advice of competent.

    I want to work at the same time, the two overlapped Flickable.
    Or flick while, I want to do the child elements.

    I know that it is to look at the source code of Flickable, may be set to False to setKeepMouseGrab.

    However, the way that I do not know.

    Although I think I have to modify the source code to rebuild the Qt library,
    If can, I do not want it

    Are looking for a way to realize the only description of QML source code.

    I also want to inform Flickable child elements mouse signals during operation.
    I do not want to modify the library for so small a matter.


  • Moderators

    Quite hard to understand your post, but I think what you are looking for is:
    @
    Flickable {
    interactive: false
    }
    @



  • sierdzio thanks for replay.

    If false the interactive property, flick operation is not accepted it.

    @
    Flickable {
    id:parent1
    flickDirection:horizontal

    Rectangle{
    Flickable{
    x:0
    width:1000
    id:child1
    flickDirection:vertical
    }
    Flickable{
    id:child2
    x:1000
    width:1000
    flickDirection:vertical
    }
    }
    }
    @

    during operation is parent1,child1,child2 can not be operated.
    and during operation is child1, parent1 can not be operated.

    I want to work at the same time and both child1/parent1. or child2/parent1


  • Moderators

    You have to decide and force Flickable into submission, but it will not magically do what you want it to :)

    What I would do here, probably (apart from maybe rethinking the design), is to set partent1.interactive to false when any of the children Flickables are operating (in onFlicking slot, or onFlickingStarted and onFlickingStopped), and then turn it on again. You can also introduce some delay to the whole process, so that the user is not confused. But I'm not sure.

    Alternative, more akin to what you want to achieve, would be to force Flickable (in children) not to accept the drag events, so that it continues up the hierarchy and is invoked in parent1, too.


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.