Not enough time for notification messages.
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Do |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
I find that the notifications for the microblogging plugin are not displayed for long enough. I expect this problem to exist with other plugins, but can't think of another example that uses the notification to test things out.
Via the mailing list, David explained that the amount of time they're displayed is based on the lenght of the message. I feel that my inability to process these messages is a result of my usage habits. Notifications appear in the top right corner of my desktop of ridiculous resolution. I believe that the overhead involved of noticing the message and focusing on the smaller text is the reason I'm having trouble reading messages before they disappear.
Could we get a pair of notification display length options as global preference throughout Do? One to set the constant overhead, and another to set the time per character/word. Maybe only the time/character/word one is needed, given the nature of the kind of messages Do is going to display.
I a cool way to calibrate it would be to assign Do actions to effect the setting, with confirmation of change displayed in a notice.
For example <Summon Do and match> "Display notices for longer"<return> would change the setting and display a notification message with the new setting.
Although this primarily effects plugins, it feels more like a Do core problem. Should this be moved?
| description: | updated |
| Chris S. (cszikszoy) wrote | #1 |
| affects: | do-plugins → do |
| Changed in do: | |
| importance: | Undecided → Wishlist |
| Changed in do: | |
| status: | New → Confirmed |
Right now the length of time a notification is displayed for correlates to the number of words in the message. It would be possible to add a scale factor here, to increase or decrease, but this option will never, ever be on any config page, or some sort of do action. I think the most we would ever consider doing is letting this setting live inside GConf, so people can manually change it if they want. But otherwise, don't expect to see this setting anywhere in the UI.