GNOME Bugzilla – Bug 791775
Rework notifications
Last modified: 2019-03-20 10:40:58 UTC
Created attachment 365736 [details] [review] Davi’s patch from bug 731750. The user should be clearly understanding what’s happening when it is asked, for example, to reload the view. So we should have enough messages to cover all the cases, and the most important message should be always displayed until activation (or view change). Also, there’s currently a bug where doing: gsettings set ca.desrt.dconf-editor.Settings sort-folders \'first\' gsettings set ca.desrt.dconf-editor.Settings sort-folders \'mixed\' gsettings set ca.desrt.dconf-editor.Settings sort-folders \'first\' gsettings set ca.desrt.dconf-editor.Settings sort-folders \'mixed\' changes the notification displayed.
Created attachment 365752 [details] [review] Fix order change confused as content change The bug showed my assumption about the order was invalid, so I changed to a O(n²) all-against-all check. If it gets too slow for very large folders, we can come up with some better solution.
Comment on attachment 365752 [details] [review] Fix order change confused as content change (In reply to Davi from comment #1) > The bug showed my assumption about the order was invalid, so I changed to a > O(n²) all-against-all check. If it gets too slow for very large folders, we > can come up with some better solution. Thanks! it’s committed. I don’t think the speed will be a really big problem; Dconf Editor has been slow as hell during three cycles and nobody complained. ^^’
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/dconf-editor/issues/27.