Written by addiks the 3 Apr 13 at 09:02.

I have seen that in OS-X your first click to a not focussed window just gives the focus to that window and does NOT pass the click-event to that window. This really feels good and clean because you dont have to think anymore where to click to change the focus. You just click somewhere on the window and it gets focus, nothing else. It feels like you have way more control and precision in your workflow.

Of course this needs to be configurable/deactivatable because it is a big change in the feel of the whole system.

I have seen that in OS-X your first click to a not focussed window just gives the focus to that window and does NOT pass the click-event to that window. This really feels good and clean because you dont have to think anymore where to click to change the focus. You just click somewhere on the window and it gets focus, nothing else. It feels like you have way more control and precision in your workflow. Of course this needs to be configurable/deactivatable because it is a big change in the feel of the whole system.

Written by m5taha5m the 1 May 13 at 18:40.

In the name of God
Salaam,
We can set an ability to change focus to other windows without passing the click-event by settings like touchpad gestures. Forexample when we click on a window with 3-fingers, then we change focus to window without passing click-event.

In the name of God Salaam, We can set an ability to change focus to other windows without passing the click-event by settings like touchpad gestures. Forexample when we click on a window with 3-fingers, then we change focus to window without passing click-event.

Written by Akiva the 1 Mar 13 at 01:28.

See Mockup
http://people.ubuntu.com/~komputes/term_within_dash.png

See Mockup http://people.ubuntu.com/~komputes/term_within_dash.png

Written by Akiva the 1 Mar 13 at 01:37.

Quote from http://askubuntu.com/questions/259234/where-do-i-find-a-terminal-lens-for-unity :
"""Which gives me the idea that sort of lens could fully replace the Alt+F2 functuonality. One could have one line of command history/search results (same style as currently displayed when pressing the key combination) and full blown terminal output a little bit below (as in my picture). – con-f-use Feb 21 at 17:01"""

From what I understand, he proposes a work around that would basically provide a snapshot of the output to display in the lens.

Quote from http://askubuntu.com/questions/259234/where-do-i-find-a-terminal-lens-for-unity: """Which gives me the idea that sort of lens could fully replace the <kbd>Alt</kbd>+<kbd>F2</kbd> functuonality. One could have one line of command history/search results (same style as currently displayed when pressing the key combination) and full blown terminal output a little bit below (as in my picture). – con-f-use Feb 21 at 17:01""" From what I understand, he proposes a work around that would basically provide a snapshot of the output to display in the lens.

Written by Akiva the 6 Mar 13 at 15:07.

A partial solution as per the comment below:
"Personally, I'd like to see "sudo" modified to detect when it's being run in a context where there's no terminal to input the password, and to call up a GUI version in that context. But I'm not sure how plausible that is. "
-Aielyn

While not displaying the code, this would solve the issue with some sudo scripts, such as adding a ppa. Just to clarify, the "Authenticate" window is the password prompt which pops up when you run synaptic package manager.

A partial solution as per the comment below: "Personally, I'd like to see "sudo" modified to detect when it's being run in a context where there's no terminal to input the password, and to call up a GUI version in that context. But I'm not sure how plausible that is. " -Aielyn While not displaying the code, this would solve the issue with some sudo scripts, such as adding a ppa. Just to clarify, the "Authenticate" window is the password prompt which pops up when you run synaptic package manager.

Written by addiks the 14 Mar 13 at 13:53.

If you want sudo rights within the Alt+F2 Unity Terminal, you can use the program gksu, which will create a popup window asking for the password.

Used like: "gksu apt-get update"

If you want sudo rights within the Alt+F2 Unity Terminal, you can use the program gksu, which will create a popup window asking for the password. Used like: "gksu apt-get update"

Written by addiks the 14 Jan 13 at 12:53.

What i currently do to achieve that goal is that i use the program 'ginn' with a custom 'whiches.xml' file. But ginn does not work with the vanilla (raw/untouched) version of unity, because unity grabs and locks the root multitouch handle(s) of the system. To resolve that i have written a script which downloads ('apt-get source unity') the unity sources, patches the sources to disable multitouch, build the packages and installs them. (I have also patched ginn, but that again is another story. I can provide the whole patcher-package if someone is interested.)

That process is very annoying because everytime unity gets updates i have to kill ginn (otherwise the updated/unpatched unity crashes after update because it cannot grab MT), update unity, run the patcher und do a 'unity --replace', all manually.

The cheapest solution would be to provide a configuration in a file or even a simple flag-file that disables multitouch in unity completely. You would create a file '~/.unity/disableMultitouch.flag' and the problem is gone, unity does not use multitouch anymore. You can run whatever multitouch program you want to.

This solution also would not interfere with beginners because they would never get the idea to create such a file. Its just a helper for developers who like to customize their system.

The file that needs to be patched for this to work is in the 'unity' package, in the sources the file '/plugins/unityshell/src/unityshell.cpp' in the method UnityScreen::InitGesturesSupport (currently line 3383-3407).

What i currently do to achieve that goal is that i use the program 'ginn' with a custom 'whiches.xml' file. But ginn does not work with the vanilla (raw/untouched) version of unity, because unity grabs and locks the root multitouch handle(s) of the system. To resolve that i have written a script which downloads ('apt-get source unity') the unity sources, patches the sources to disable multitouch, build the packages and installs them. (I have also patched ginn, but that again is another story. I can provide the whole patcher-package if someone is interested.) That process is very annoying because everytime unity gets updates i have to kill ginn (otherwise the updated/unpatched unity crashes after update because it cannot grab MT), update unity, run the patcher und do a 'unity --replace', all manually. The cheapest solution would be to provide a configuration in a file or even a simple flag-file that disables multitouch in unity completely. You would create a file '~/.unity/disableMultitouch.flag' and the problem is gone, unity does not use multitouch anymore. You can run whatever multitouch program you want to. This solution also would not interfere with beginners because they would never get the idea to create such a file. Its just a helper for developers who like to customize their system. The file that needs to be patched for this to work is in the 'unity' package, in the sources the file '/plugins/unityshell/src/unityshell.cpp' in the method UnityScreen::InitGesturesSupport (currently line 3383-3407).

Written by addiks the 21 Jan 13 at 18:10.

As an alternative to a text-file or flag-file configuration (which isn't very beginners-friendly), there could be a way to configure and/or disable multitouch in the GUI system-settings like with the current custom keyboard shortcuts and a simple switch (checkbox, button, slider, ...) to disable multitouch in unity completely so another multitouch-program like ginn can be used. This is not as cheap to implement as #1 but the result would be easier to use for everyone.

As an alternative to a text-file or flag-file configuration (which isn't very beginners-friendly), there could be a way to configure and/or disable multitouch in the GUI system-settings like with the current custom keyboard shortcuts and a simple switch (checkbox, button, slider, ...) to disable multitouch in unity completely so another multitouch-program like ginn can be used. This is not as cheap to implement as #1 but the result would be easier to use for everyone.