As per any enumeration you need to specify the class also:

         flickDirection: Flickable.HorizontalFlick

This may not be well explained in the documentation - worth filing a bug.

Martin.



On Tue, 4 May 2010 05:01:23 pm ext [email protected] wrote:
> Hi,
> 
> Could someone tell me when do we get control to onFlickStarted:{}
> onFlickEnded:{} ?? import Qt 4.6
> 
> Rectangle {
> 
>  width: 400
>  height: 400
>  color: "lightblue"
> Flickable {
>         width: 320
>         height: 480
>         contentWidth: image.width
>         //contentHeight: image.height
>         flickDirection: HorizontalFlick                   ---->>>>>  Unable
> to assign [undefined] to int interactive: true
>         clip: true
>         Rectangle {
>             id:image
>             width: 200
>             height: 200
>             color: "black"
>             Text {
>                 x: 66
>                 y: 93
>                 text: "Hello World"
>                 color: "white"
>             }
>         }
>         onFlickStarted:{
>             console.log("start contentx"+contentX)
>             console.log("start contenty"+contentY)
>         }
>         onFlickEnded:{
>             console.log("end contentx"+contentX)
>             console.log("end contenty"+contentY)
>         }
>     }
> }
> 
> What's wrong with this code?? Please do provide more examples and update
> the documentation
> 
> Thanks and Regards,
> Rakesh.M
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On
> Behalf Of Martin Jones Sent: Thursday, April 22, 2010 9:15 AM
> To: [email protected]
> Subject: [Qt-qml] Flickable overshoot property becomes boundsBehavior
> 
> So that we can add the DragOverBounds behavior.
> 
> - StopAtBounds - the contents can not be dragged beyond the boundary of the
> flickable, and flicks will not overshoot. - DragOverBounds - the contents
> can be dragged beyond the boundary of the Flickable, but flicks will not
> overshoot. - DragAndOvershootBounds (default) - the contents can be
> dragged beyond the boundary of the Flickable, and can overshoot the
> boundary when flicked.
> 
> This will affect QML releases after the 4.7.0 beta.
> 
> --
> Martin
> _______________________________________________
> Qt-qml mailing list
> [email protected]
> http://lists.trolltech.com/mailman/listinfo/qt-qml

-- 
Martin
_______________________________________________
Qt-qml mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-qml

Reply via email to