growl-for-windows
growl-for-windows copied to clipboard
Published
20 hours ago •
briandunnington
briandunnington
Missed Notifications Do Not Store URL Callbacks
Repro:
1. Miss a notification that has a URL callback
2. Click on it
Expected:
Uses URL callback to open browser.
Current behavior:
Nothing. Just highlights the notification.
Version: 2.0
OS: XP SP2
Comment:
I understand callbacks in missed notifications doesn't make sense because
of active sockets. URL callbacks do make sense because they do not maintain
a socket connection to the application.
Original issue reported on code.google.com by [email protected] on 12 Mar 2010 at 9:39
i agree completely that it would be nice to be able to trigger URL callbacks
from the
missed notification window (and even the History tab); the only problem i have
is
that most users dont know/dont care which type of callback was specified, so
some
notifications that would normally trigger a callback (socket) wont anymore, but
others (url) still will.
it is really easy for me to make the missed/historic url callbacks trigger - i
just
have to work out it out from the user experience side of things.
Original comment by [email protected] on 13 Mar 2010 at 1:50
Why not hide it? What I mean by that is don't introduce something that is a
default
behavior. Perhaps just a context menu from a right click that would display the
callback type and potentially an option to invoke it?
This suggestion is more of a "don't worry about the real problem for everyone,
but
offer it to people that are looking for it".
Original comment by [email protected] on 17 Mar 2010 at 10:18
Issue 33 has been merged into this issue.
Original comment by [email protected] on 22 Dec 2010 at 11:21
Any idea if this is still happening? If it's easy to add, it would be really
useful if we could click on the 'missed' notifications.
Original comment by [email protected] on 19 Nov 2013 at 1:52
Is this project still live? If so is it possible to introduce URL callbacks for missed notifications as detailed in this issue?
