Bug 426633

Summary:	Notifications Timeout starts earlier than expected
Product:	[Frameworks and Libraries] Snoretoast	Reporter:	brute4s99 <piyushaggarwal002>
Component:	general	Assignee:	Hannah von Reth <vonreth>
Status:	REPORTED ---
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description brute4s99 2020-09-17 09:52:00 UTC

SUMMARY
I've noticed that if multiple notifications are invoked from kdeconnect thru snoretoast, the timeout is counted from the point the SnoreToast.exe is executed, and not from the point when the notification is actually shown to the user.

STEPS TO REPRODUCE
1. start multiple notifications from snoretoast
2. wait for them to time out

OBSERVED RESULT
all notifications are timed out from the point they were invoked (if a previous notification is currently on display, the timeout for a newer keeps running while it's not visible to the user)

EXPECTED RESULT
notifications are timed out starting from the point they actually show up.

SOFTWARE/OS VERSIONS
Windows: 10
KDE Frameworks Version: master as on time of writing
Qt Version: 5.15