#22 Notifications get "stuck" as unread

[Anonymous]

Hi, thanks for the nice tool, yet it only works for me for some time after it is started - it shows the updates as needed. Yet then at some point the notifications are no longer updated - until I restart the tool.

For example, I now have it show two wave updates that happened yesterday afternoon - I have since read those waves (and marked them as "read" in the Google Wave), and new waves were added and updated by other people - yet I no longer see that from the Wave Notifier. Other members of my team are seeing the same behaviour, on a variety of OSes (though I am using Windows 7). For us this makes the tool unusable, as one needs to keep watching the Google Wave site to check whether what the tool displays is relevant or not anymore, so I would really appreciate if you could look into fixing this problem.

Thank you!
Anton

[Anonymous]

Forgot to say - this is in 10.2.5.44 (otherwise I wouldn't be able to logon).

[Pieter van Ginkel]

Thank you for creating the bug. I have some questions concerning this issue.

* Is the problem persistent for all waves, or are there waves which do receive updates after some time;
* Does the tray icon change it's icon to the one with the "unread waves" overlay (the small white triangle);
* Does the flyout (left-click once on the tray icon) reflect that the wave has been updated?

[Pieter van Ginkel]

And could you please also verify that the "new waves" sound is being played? This last is a queue that a popup will be shown. The problem could lie in that the popups are being blocked from being displayed and verifying whether the sound is being played is a clear indication that the latter is the problem.

[Pieter van Ginkel]

Could you please try the version located at http://wave-notify.googlecode.com/svn/releases/10.2.11.46/wave-notify-10.2.11.46.exe and see whether this solves your problem. This is an intermediate test version which addresses an issue which could help you.

After installing this version, you will automatically be upgraded to the latest release when a new version becomes available. If you have problems with this test version, please install the latest release from the sourceforge page.

[Pieter van Ginkel]

Sorry for all the comments, but I've just put a new version online. This is the next version for the version of the last comment.

You should be automatically updated to this new version. Please verify whether this version still has this problem and, if so, follow the steps I've lined out in the earlier comment.

[Anonymous]

Thanks for all the feedback, I've installed v47, and will write here if the problem happens again, and will also try to watch out for the signs that you posted below.