Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • P Plasma Workspace
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 18
    • Issues 18
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 90
    • Merge requests 90
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Plasma
  • Plasma Workspace
  • Repository

Switch branch/tag
  • plasma-workspace
  • libnotificationmanager
  • notificationsortproxymodel.cpp
Find file BlameHistoryPermalink
  • Kai Uwe Broulik's avatar
    [Notifications] Don't take updated time into account for sorting · d7118124
    Kai Uwe Broulik authored May 18, 2020
    Notification spec says, when replacing a notification:
    
    > The server must atomically (ie with no flicker or other visual cues) replace the given notification with this one.
    
    Notifications shifting about is a "visual cue".
    
    Differential Revision: https://phabricator.kde.org/D29771
    d7118124

Replace notificationsortproxymodel.cpp

Attach a file by drag & drop or click to upload


Cancel
GitLab will create a branch in your fork and start a merge request.