https://bugs.kde.org/show_bug.cgi?id=445512
--- Comment #11 from Jin Liu <ad.liu....@gmail.com> --- Found a "workaround": force the code to re-create listview when switching categories, instead of reusing views and restoring bindings. diff --git a/applets/kickoff/package/contents/ui/ApplicationsPage.qml b/applets/kickoff/package/contents/ui/ApplicationsPage.qml index 0987ce175..4403796e9 100644 --- a/applets/kickoff/package/contents/ui/ApplicationsPage.qml +++ b/applets/kickoff/package/contents/ui/ApplicationsPage.qml @@ -106,7 +106,7 @@ BasePage { // TODO: maybe find a way to have a list view with grids in each section? stackView.replace(applicationsListViewComponent) } else if (root.sideBarItem.currentIndex > 1 - && stackView.currentItem.objectName !== stackView.preferredAppsViewObjectName) { + /*&& stackView.currentItem.objectName !== stackView.preferredAppsViewObjectName*/) { stackView.replace(stackView.preferredAppsViewComponent) } } However this is only a hack. It causes visible flicking. So I guess that's why views are reused there in the first place. But that's a hint that there might be some timing/sequencing issue among RestoreBinding, currentItem.forceActiveFocus and mouse hovering, which caused "currentItem" drawn in the old model while the rest in the new model? -- You are receiving this mail because: You are watching all bug changes.