© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
I've looked into this a bit. Seems there's a change in behaviour between Qt5.5 and 5.6 in how the Flickable's contentItem->width is initially set - and this impacts the LVWPH
Try this demo Qt5.6 and LVWPH:
http://
If you use anchors.fill, the contentItem width stays at 0. But setting width explicitly yields a correct contentItem width. I presume there's a widthChanged signal somewhere that needs to be listened to.