unity-design team mailing list archive

[mac_v <drkvi-a@xxxxxxxxx>]

On Thu, 2009-08-27 at 14:46 -0700, Mike Rooney wrote: 
> I feel ambivalent regarding the vertical positioning, but I do agree
> that "fixing" notifications to not fade if they appear where the mouse
> is, is actually breaking it. 
> 
On Thu, 2009-08-27 at 21:20 -0500, Paulo J. S. Silva wrote: 
> 2009/8/27 Steve Dodier <sidnioulz@xxxxxxxxx>:
> > I think it shouldnt cost so much to fade it when it spawns unfaded because
> > of the mouse. Having to leave the area 40px around the bubble and to come
> > back into it to blur the bubble is overkill. I'd prefer having it spawn
> > unfaded and fading after one or two seconds, or directly beginning to slowly
> > fade.
> >
> 
> The elegance of the notifications is that they try to be unobtrusive.
> The described user case where the bubble appeared on the region where
> the cursor was so that the user had to stop working to wait for the
> bubble go away looks like a nightmare.
> 
> +1 Move the bubbles back to the top.
> +1 The bubble should appear "faded" if the mouse is already in its area.
> 
> Paulo
> 
> _______________________________________________

I absolutely disagree on reverting to fade-on-appearance , 
The *only* reason the bubbles are now a disturbance is because of the
position and not the do-not-fade-on-appearance.

Earlier, I have noticed several bubbles just did not appear , since the
pointer was positioned on close/minimize/maximize.

[You might wonder how would i know if it was not appearing? , its
because i had compiz animations for the bubbles set to burn-on-close ,
so , all i would see is a burn animation of a bubble which just did not
appear!]

*The no-fade-on-appearance is a wonderful move* .And so are the other
recent changes which have been done.

*The only bad move was the position* . Regarding the position, my
suggestion would be to:

- Move both the bubble classes back up , [sync and async]

This would avoid:
- the async bubbles [second row]from 
 * blocking the Firefox Search box 
 * blocking when a user has the pointer on close/minimize/maximize
 * blocking any potential work space. 

- Since the first row is the sync notification , it wouldn't matter if
it blocks the above locations. Because the user has triggered them on
his due to some interaction and it wouldnt bother him.

The second row for async bubbles is a better location than the middle of
the screen , which will almost always get in the face of the user!

-- 
Cheers,
mac_v