by setting a ListView (or a GridView) as the mainItem
of an OverlaySheet, it uses it instead of an internal Flickable
due to limitations of ListView, in that case it always takes 100% of the
page width
Details
- Reviewers
apol - Group Reviewers
VDG Plasma Kirigami - Commits
- R169:2f62fbbcd566: possible to use OverlaySheet with ListView
Diff Detail
- Repository
- R169 Kirigami
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
We've been looking into it with @colomar and we like how it works. We think it would be useful if we'd get a small margin on either side so that it's easy to close when we're half-way through the scrolling process.
Other than that, +1
as i explained, on the case of a listview, i can't make it narrower than the page, because of how listview works, i can't have the touch sensitive area being wider then the list itself, so clicking outside the list on the sides wouldn't dismiss it, while it would when clicking on top or bottom (it's structural in the ListView c++ stuff, so belongs on the "don't even try" category).
But this makes the sheet become rather hard to dismiss. I'd say let's get this in, as the current component just breaks awkwardly, and then we'll see how to make it usable, possibly from the application itself.
There is always still the possibility to use one of the Action Buttons as a close button (as shown in the Gallery) if it gets too long to easily swipe away.
There is always still the possibility to use one of the Action Buttons as a close button (as shown in the Gallery) if it gets too long to easily swipe away.
i could try to hack there mouseareas that would dismiss and move the listview to make it look as the flickable is whole (probably no actual flicking tough)
it would be a lot of very ugly qml logic, but maybe could work