PhilMurwin / growl-for-windows

Automatically exported from code.google.com/p/growl-for-windows
0 stars 0 forks source link

New Feature: Falloff time for notifications #24

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
-

What is the expected output? What do you see instead?
If there are many notifications (e.g. via the outlook plugin) most of the 
displays are fading the notifications out too fast. It is often difficult 
to read all notifications before they are removed.
Maybe the Display Interface in the SDK can be updated, so all new display 
versions have to support a setting specifing the amount of time a 
notification has to be visible before it is removed.

What version of the product are you using? On what operating system?
All growl displays, especially Frozencow's translucentdark Display 1.7 in 
conjunction with the outlook plugin.

Please provide any additional information below.

Original issue reported on code.google.com by t0bit0b...@gmail.com on 24 Jan 2010 at 1:48

GoogleCodeExporter commented 9 years ago
on the Application tab, there is a setting for 'Duration'. by default, the 
display
decided how long the notification is visible before closing. by changing the 
Duration
value, you can tell the display to leave the notification on the screen for a 
longer
period of time.

each display has to honor this value for it to work. all of the built-in 
display use
the value, and i think TranslucentDark does as well, but if not, i will report 
the
issue to FrozenCow.

Original comment by briandun...@gmail.com on 25 Jan 2010 at 8:10

GoogleCodeExporter commented 9 years ago
I am sorry, my fault. The Duration setting works fine. Please close this issue. 
Sorry for any inconvenience. 

Original comment by t0bit0b...@gmail.com on 26 Jan 2010 at 6:30

GoogleCodeExporter commented 9 years ago
no problem. glad to help.

Original comment by briandun...@gmail.com on 3 Feb 2010 at 6:27