Fades causing issues

[Christopher Forsythe]

Guys and girls,

On the forums there has been a longstanding thread about the fade-in/out causing issues:

http://forums.cocoaforge.com/viewtopic.php?f=6&t=16321

Could each of you take a look at it and come up with possible solutions to the problems there? The most obvious to me is to provide a defaults command to just disable the fades, but I think we have a bigger underlying problem that needs to be addressed, I'm just not seeing it though.

Chris

[Peter Hosey]

On Sep 19, 2008, at 12:05:52, Christopher Forsythe wrote:
> Could each of you take a look at it and come up with possible
> solutions to the problems there? The most obvious to me is to
> provide a defaults command to just disable the fades, but I think we
> have a bigger underlying problem that needs to be addressed, I'm
> just not seeing it though.

First off, when closing a notification, we should dramatically shorten
the fade-out time. I'm thinking 1/10 second, but we can play around
see what looks good, then set it a little below that.

The long-term solution is more transitions with a pref to choose for
each visual display.

- No transition (appear/disappear instantly)
- Fade
- Pop in/out (like iPhone)
- Slide in/out

At some point, we could add a plug-in type to add new transitions.

[Christopher Forsythe]

A plugin type might be going too far, but I agree with the rest. It would fit into the whole display profiles type of design I want us to head towards at some point too.

I think we should look into the fades stuff for 1.3 or 1.4.

[Jay Levitt]

I'm new to both Growl and Objective-C (and Cocoa, for that matter),
but I'm thinking of taking a crack at this in a few weeks - at least a
proof-of-concept - since the fading really bugs me.

It looks like the magic happens in GrowlWindowTransition, which sets
up an NSAnimation but doesn't set any transition time. So I'd need to
start there, and percolate a new GrowlWindowTransitionTime:

1. down to GrowlFadingWindowTransition (and/or any other transitions),
and
2. up and out to plugins and/or a global Growl preference.

Does that sound roughly right? If anyone's given this any thought,
even of the "I must remember to do X when I play with this", I'd
appreciate your brain dump.. otherwise, I'll just see what happens.

Jay Levitt

[Peter Hosey]

On Oct 09, 2008, at 06:05:25, Jay Levitt wrote:
> It looks like the magic happens in GrowlWindowTransition, which sets
> up an NSAnimation but doesn't set any transition time.

It doesn't set up an NSAnimation; it *is* an NSAnimation. (I don't
know why it's not an NSViewAnimation.) So, you should be able to make
this work simply by sending setDuration: to the animation from the
Growl<Display's name>WindowController class.