quote:
Originally posted by cloudhunter
quote:
Originally posted by SpunkyLoveMuff
quote:
Originally posted by cloudhunter
A compromise: How about it detects when the toast is pressed, and if it is, stops showing the toasts
When would the toast next be displayed? 
Hmm, didn't think of that one
Hi and thanks for your input
I've come up with a solution , of a bogus sort ,what happens is that it displays the toast only once, and doesnt display it while it read that there are still NEW <whatever triggerd the toast> , so for instance if NEW messages triggered it NEW comments will still trigger it.
Now heres the clever part , it keeps the toasts untriggered while the NEW <whatever> message is recieved (indicating that they havent been seen) , BUT if it gets no NEW <whatever> following a s NEW <whatever> (indicating its been seen) it resets itself , so that the next NEW will trigger an event.
HOWEVER for this means that the Notifier might miss NEW notifications if a new message is sent within a minute as thats the fequency it polls at, if you read a message and replied and got a reply in less than a minute (very possible) it would think the new reply and the coresponding NEW <message>was just the old NEW notifier. This goes for All the notifiers
THis meand the user might not be notified of events , which was the whole point really. Maybe I could implement this as an option with a warning of low accuracy of reporting things happening within a minute , or frequency of each other?
/ –
