Workaround for the bug where old notifications could not be erased
This commit is contained in:
parent
6ce0b6b874
commit
8c7c95f98b
1 changed files with 5 additions and 2 deletions
|
@ -137,8 +137,11 @@ void NotificationsDbusInterface::dismissRequested(Notification* notification)
|
|||
np.set<QString>("cancel", internalId);
|
||||
mPlugin->sendPackage(np);
|
||||
|
||||
//This should be called automatically back from server
|
||||
//removeNotification(internalId);
|
||||
//Workaround: we erase notifications without waiting a repsonse from the
|
||||
//phone because we won't receive a response if we are out of sync and this
|
||||
//notification no longer exists. Ideally, each time we reach the phone
|
||||
//after some time disconnected we should re-sync all the notifications.
|
||||
removeNotification(internalId);
|
||||
}
|
||||
|
||||
QString NotificationsDbusInterface::newId()
|
||||
|
|
Loading…
Reference in a new issue