The behavior exposed to QML is identical to what QSortFilterProxyModel offers - what you can't do in QML is override filterAcceptsRow or lessThan respectively. So the question becomes what use cases to support in a way that doesn't become potentially slow Javascripts running whenever the model changes. See http://doc.qt.io/qt-5.4/qsortfilterproxymodel.html#filterAcceptsRow
We could potentially allow setting a list like sort.property ["foo", "bar"] if we assume the search term to be one, but that may not be enough? Some sample use cases might be good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1488823 Title: SortFilterModel: No complex "OR" or "AND" sorting possible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1488823/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
