I have problem with disposing of tray notification. It should get invisible by default after delayMsec=3000. But when I do not change my mouse position - it does not. Could you explain me how it works ?
Second, more important problem is when I create many tray notification at once. It looks that it works nondeterministically: some times all notifications gets invisible one-by-one. Other times few of them are visible until I press them by a mouse button.
I create notification by a method getMainWindow().showNotification(“”, “text”, Notification.TYPE_TRAY_NOTIFICATION);
The notifications wait for the user to interact with the application before they disappear, so that you can be sure that the user is not away getting coffee or something like that.
As for the multiple notifications, they should disappear one at a time, using the same rule (requires interaction with the application each time), which allows the user to see each one. You should avoid displaying many notifications at once, however - they are not designed for that, the one-at-a time is just a fallback if you for some reason get multiple notifications by mistake (hopefully a future version will handle multiple simultaneous notifications better, although you should still beware of overuse).
There are some alternatives in the Directory as well, for instance
TemporaryLabel , and I know Sami is about to publish a great-looking add-on that addresses the same problem.
Inline labels can be a better solution sometimes, overlaid notifications other times - usability should dictate which solution to choose.
Tray notifications were working properly for me until I upgraded from 7.1.12 to 7.3.5. As Marc mentioned, the default behavior was to remain up until the user started typing or clicking, and then fade away. Now they stay up until the user explicitly clicks on them. The behavior is unchanged when I use setDelayMsec. I set the delay to 3000 msec, hoping for a 3-second display, or maybe even a 3-second display after the user starts interacing. No change. The setDelayMSec call doesn’t seem to do anything. This behavior is the same on IE 11, ffox and chrome.