Re: [Ayatana] What to do with the menubar on non-full screened windows.

2011-03-30 Thread SorinN
Klevin, you say : No, it would take more clicks than the expected, I think that, if not my idea, the button on titlebar is handlier than this. , talking about the show / hide menu-bar button. It will not take many clicks because if I need to see the menubar I click the button and the menubar

Re: [Ayatana] What to do with the menubar on non-full screened windows.

2011-03-30 Thread Matthew Paul Thomas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Saleel Velankar wrote on 29/03/11 15:16: In a nonmaximized window on a. a large screen b. with other nonmaximized windows present The global-menubar fails for these reasons. 1. Confusion on which application the menu is for. This is a bug in

Re: [Ayatana] window and workspace management in unity

2011-03-30 Thread Greg K Nicholson
This is already implemented in Compiz's Scale Addons plugin. Another, complementary approach would be to have a lower limit for the zoom factor when scaling—say, around 2/3—and clip windows if necessary to only show the top-left corner (top-right in RTL locales).

Re: [Ayatana] What to do with the menubar on non-full screened windows.

2011-03-30 Thread SorinN
Matthew If it's an obscene amount, your pointer acceleration settings are wrong: you'll have just as much trouble getting to the Ubuntu button, the Trash, or the session menu. The obscene amount is still there - you can not cut it out in just 3 words. It would be easy of course to solve

Re: [Ayatana] What to do with the menubar on non-full screened windows.

2011-03-30 Thread Ian Santopietro
I use Unity on a 23 full HD monitor, and I don't find it tiring to move the mouse to the menu at all, and I use it a minimum of 8 hours per day. On Mar 30, 2011 3:34 PM, SorinN nemes.so...@gmail.com wrote: ___ Mailing list: https://launchpad.net/~ayatana

Re: [Ayatana] What to do with the menubar on non-full screened windows.

2011-03-30 Thread SorinN
Sure if we compare individual by individual experience we are just few millions here - each with the best theoretic argument. That's why this argument should be probably the last fire in the battle. Fortunately Usability is a science which work with other values. 2011/3/31 Ian Santopietro

Re: [Ayatana-commits] [Merge] lp:~karl-qdh/indicator-datetime/propupdatefail into lp:indicator-datetime

2011-03-30 Thread Karl Lattimer
I can't reproduce the bug at all so this was the only inconsistency which *could* have matched the fact that the show seconds was triggering an update but the change in format wasn't. Remove the inconsistency, hopefully the bug's gone. --

[Ayatana-commits] [Merge] lp:~mterry/indicator-datetime/more-error-icons into lp:indicator-datetime

2011-03-30 Thread noreply
The proposal to merge lp:~mterry/indicator-datetime/more-error-icons into lp:indicator-datetime has been updated. Status: Needs review = Merged For more details, see: https://code.launchpad.net/~mterry/indicator-datetime/more-error-icons/+merge/55532 --