From 5c83d292a2a09af41c4a7dab36010ce9b31cdb80 Mon Sep 17 00:00:00 2001
From: Kai Uwe Broulik <kde@privat.broulik.de>
Date: Wed, 29 May 2019 13:47:31 +0200
Subject: [PATCH] [Notifications] Don't replace last one if next one is
 identical

Since there is timeout for when it is considered a separate notification and we don't even close the previous one properly.
Just remove that stopgap and if we need something like this again, do it properly.

Differential Revision: https://phabricator.kde.org/D21473
---
 libnotificationmanager/notificationsmodel.cpp | 13 -------------
 1 file changed, 13 deletions(-)

diff --git a/libnotificationmanager/notificationsmodel.cpp b/libnotificationmanager/notificationsmodel.cpp
index 6f8168816..405f4f4b2 100644
--- a/libnotificationmanager/notificationsmodel.cpp
+++ b/libnotificationmanager/notificationsmodel.cpp
@@ -83,19 +83,6 @@ NotificationsModel::Private::~Private()
 
 void NotificationsModel::Private::onNotificationAdded(const Notification &notification)
 {
-    // If we get the same notification in succession, just compress them into one
-    if (!notifications.isEmpty()) {
-        const Notification &lastNotification = notifications.constLast();
-        if (lastNotification.applicationName() == notification.applicationName()
-                && lastNotification.summary() == notification.summary()
-                && lastNotification.body() == notification.body()
-                && lastNotification.desktopEntry() == notification.desktopEntry()
-                && lastNotification.applicationName() == notification.applicationName()) {
-            onNotificationReplaced(lastNotification.id(), notification);
-            return;
-        }
-    }
-
     // Once we reach a certain insane number of notifications discard some old ones
     // as we keep pixmaps around etc
     if (notifications.count() >= s_notificationsLimit) {