For teh sake of QQC2 compatibility, let's call the property 'pressed'.
Scrollbars are exposed by ScrollView, so there's no need to expose there
anything.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
@Andrea - Sure, no problem! ;)
@Tim - Yes, checking for e.g. 'verticalVelocity' property of the
Flickable could accomplish it. QQC2 are not provided with the Ubuntu UI
Toolkit and they are available only with Qt 5.7, so I would prefer a
solution which can be easily integrated in a Ubuntu
Would there be any other ways to show the overlay? For example by
flicking the Flickable really fast? Then maybe it is better to use a
property of the flickable.
Also, to keep the APIs consistent, maybe there should be property
'pressed' which is similar to MouseArea.pressed. Also, we can have a
^ Using the API of QQC2 Scrollbar you can accomplish what you want. In
onPositionChanged, you can check if 'pressed' is true and then enable
the overlay. You can hide the overlay again when pressed becomes false.
--
You received this bug notification because you are a member of Ubuntu
Touch
Hi Stefano,
thank you for this report. I'll bring this up with the SDK team and see
if we can "afford" providing (which means guaranteeing future
compatibility for) that property ;)
Can you please ping me again on Monday about this?
--
You received this bug notification because you are a
5 matches
Mail list logo
