e.g. to simplify dependencies? ex: QAction-like in QtGui
Description
Description
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | None | T11555 Requesting changes in Qt | ||
| Open | None | T12041 KDeclarative: kill own drag and drop handling | ||
| Open | None | T12010 Replace KLocalSocket[Server] in KIO by QLocalSocket[Server] | ||
| Open | None | T12032 Future of KStatusNotifierItem | ||
| Open | None | T12359 Use Q_PROPERTY RESET more | ||
| Open | None | T12218 Try to get PositiveColour/NegativeColour/NeutralColour into QPalette upstream |
Comment Actions
While many methods in QAbstractItemModel, including QModelIndex are usable from QML these days, the properties on e.g. QSortFilterProxyModel all lack a NOTIFY signal. When added, those classes could more easily be used in and exposed to QML.
Comment Actions
@broulik that's an easy one that doesn't have to wait for Qt6, go ahead and submit a patch, I'll review it :-)
Comment Actions
https://codereview.qt-project.org/c/qt/qtbase/+/282297 :)
I realized the filter string stuff is a slot already so that can be used imperatively already at least.