How about the lower right corner for async and upper right corner for
sync. That way the notification bubbles will be out of the way yet
separated.
/Nicklas W Bjurman
___
Mailing list: https://launchpad.net/~ayatana
Post to : ayatana@lists.launchpad
On Mon, Aug 31, 2009 at 2:06 AM, Mirco
Müller wrote:
>
> Questions now are... should the fade-prevention still kick in, if the
> mouse pointer is hidden?
Nope, I don't think so. The user can't see the mouse and is not aware
of its position, so it will lead to a confusing experience (it took
Am Freitag, den 28.08.2009, 11:25 -0700 schrieb Mike Rooney:
> ...
> While we are on the subject of mouse cursor behavior, I just want to
> mention to keep in mind the visibility of the mouse. I noticed before
> if I am doing something which hides the mouse cursor, the notification
> would appear
On Fri, Aug 28, 2009 at 3:06 AM, Mirco
Müller wrote:
> Am Freitag, den 28.08.2009, 11:14 +0200 schrieb David Barth:
>> Mark Shuttleworth wrote:
>> > Mirco Müller wrote:
>> >
>> > > Am Freitag, den 28.08.2009, 09:30 +0100 schrieb Mark Shuttleworth:
>> > >
>> > >
>> > >
>> > > > ...
>> > > > Mirco, i
On Fri, Aug 28, 2009 at 15:09, Vincent Arnoux wrote:
> Given that all window control widgets (minimize/maximize/close buttons
> and scrollbar) are on the right, I believe the mouse is almost never
> on the left side of the screen. Why not move the notifications on the
> left (top-left, middle-left
How about the lower right corner for async and upper right corner for
sync. That way the notification bubbles will be out of the way yet
separated.
Also if access to the window control icons is a problem with having
bubbles in the upper right corner, why not simply put the bubble a few
em's lower?
Dear all,
Given that all window control widgets (minimize/maximize/close buttons
and scrollbar) are on the right, I believe the mouse is almost never
on the left side of the screen. Why not move the notifications on the
left (top-left, middle-left or bottom-left) and stop worrying about
mouse point
Mark Shuttleworth wrote:
> David Barth wrote:
>
>> However, using the XScreenSaver extension, the X server is maintaining
>> this information for us, so that we can track the idle time, without
>> doing any polling, in particular when no notification is on display.
>>
>
> Yes, this gives us
Even though I concur with Neil, that is in a large screen the new
position may not be very bad, but in a small screen it is worse, let
me show my use case:
Actually, in a big screen I usually work with two windows opened side
by side (one is latex and the other evince showing me the compiled
latex
On Fri, 2009-08-28 at 12:28 +0100, Stuart Langridge wrote:
> Just so it doesn't look like everyone hates it: I like the middle-screen
> position for notifications. I don't think of them as being "associated"
> with the notification area, particularly; I don't have very many things
> actually in the
David Barth wrote:
> However, using the XScreenSaver extension, the X server is maintaining
> this information for us, so that we can track the idle time, without
> doing any polling, in particular when no notification is on display.
Yes, this gives us a binary "it has moved" or "it has been idle"
Jack Leigh wrote:
> Big fan of notify-osd overall but the new vertical placement is really
> unintuitive, due to being separated from everything it should be
> associated with and intrusive due to its position. I too thought it was
> a bug initially.
Just so it doesn't look like everyone hates it
Big fan of notify-osd overall but the new vertical placement is really
unintuitive, due to being separated from everything it should be
associated with and intrusive due to its position. I too thought it was
a bug initially.
Just so y'all know =D
Cheers,
Jack
--
Leighman | 'And, if rain brin
Am Freitag, den 28.08.2009, 11:14 +0200 schrieb David Barth:
> Mark Shuttleworth wrote:
> > Mirco Müller wrote:
> >
> > > Am Freitag, den 28.08.2009, 09:30 +0100 schrieb Mark Shuttleworth:
> > >
> > >
> > >
> > > > ...
> > > > Mirco, is there any way to know, when the notification appe
Mark Shuttleworth wrote:
> Mirco Müller wrote:
>
>> Am Freitag, den 28.08.2009, 09:30 +0100 schrieb Mark Shuttleworth:
>>
>>
>>
>>> ...
>>> Mirco, is there any way to know, when the notification appears, how
>>> long the mouse has been stationary?
>>>
>>>
>> Yes, that sh
Mirco Müller wrote:
> Am Freitag, den 28.08.2009, 09:30 +0100 schrieb Mark Shuttleworth:
>
>
>> ...
>> Mirco, is there any way to know, when the notification appears, how
>> long the mouse has been stationary?
>>
>
> Yes, that should be doable. I'll give that a try today and let you
>
Am Freitag, den 28.08.2009, 09:30 +0100 schrieb Mark Shuttleworth:
> ...
> Mirco, is there any way to know, when the notification appears, how
> long the mouse has been stationary?
Yes, that should be doable. I'll give that a try today and let you
folks know about the outcome.
> On the p
Thanks all for comments, bouquets and brickbats. We're experimenting
with different layouts and positions, and the feedback helps. It helps
more if it doesn't come dripping with sarcasm ;-).
We'll let the no-fade-when-mouse-is-there behaviour bake for a while
before making any further changes.
M
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:
> 20
2009/8/27 Steve Dodier :
> 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,
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
f
On Thu, Aug 27, 2009 at 12:19 PM, Alex Launi wrote:
> A bit ago I did my set of updates, which included the new release of
> notify-osd, which are placed a bit lower than midway down the screen.
> Putting these that far down the screen is really disrupting, and much more
> flawed than their origina
On Thu, 2009-08-27 at 15:19 -0400, Alex Launi wrote:
> A bit ago I did my set of updates, which included the new release of
> notify-osd, which are placed a bit lower than midway down the screen.
> Putting these that far down the screen is really disrupting, and much
> more flawed than their origin
A bit ago I did my set of updates, which included the new release of
notify-osd, which are placed a bit lower than midway down the screen.
Putting these that far down the screen is really disrupting, and much more
flawed than their original position. The biggest problem is that the
information they
24 matches
Mail list logo
