https://bugs.kde.org/show_bug.cgi?id=409123
--- Comment #6 from Hannah von Reth ---
The shortcut is created before, but I guess there is some magic on the Windows
side happening.
Maybe a wait would help but as the internal id is mainly for dev purpose or
simple shell scripts a missed notification
https://bugs.kde.org/show_bug.cgi?id=409123
--- Comment #5 from Daniel ---
Ok, I already though that this was the issue. I just expected the shortcut to
be created before the notification was issued, but of course it makes sense to
only run the shortcut logic when the notification fails.
Will de
https://bugs.kde.org/show_bug.cgi?id=409123
Hannah von Reth changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=409123
--- Comment #3 from Daniel ---
Ok. Bug #409124 is resolved, let's go!
For some reason it did not work the first time, but worked the second time I
executed `SnoreToast.exe -t Hello -m World`, here is the log:
First:
```
"C:\\Program Files\\SnoreToas
https://bugs.kde.org/show_bug.cgi?id=409123
--- Comment #2 from Daniel ---
```
C:\Program Files\SnoreToast\bin>where SnoreToast.exe
C:\Program Files\SnoreToast\bin\SnoreToast.exe
```
Waiting until bug #409124 is resolved before further investigation.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=409123
--- Comment #1 from Hannah von Reth ---
Hm thx for the report.
That debugview++ doesn't show anything makes me doubt that the correct
SnoreToast.exe is executed.
where.exe SnoreToast.exe
returns the correct path?
If the correct version is used, coul
https://bugs.kde.org/show_bug.cgi?id=409123
Daniel changed:
What|Removed |Added
CC||dan...@safing.io
--
You are receiving this mail becau
