| 2012-07-02 11:53:17 |
John Lea |
bug |
|
|
added bug |
| 2012-07-02 11:53:26 |
John Lea |
tags |
|
udp |
|
| 2012-07-02 11:53:31 |
John Lea |
bug task added |
|
unity |
|
| 2012-07-02 11:53:40 |
John Lea |
bug task added |
|
unity (Ubuntu) |
|
| 2012-07-02 11:53:50 |
John Lea |
ayatana-design: assignee |
|
John Lea (johnlea) |
|
| 2012-07-02 11:53:53 |
John Lea |
ayatana-design: importance |
Undecided |
Medium |
|
| 2012-07-02 11:53:57 |
John Lea |
ayatana-design: status |
New |
Fix Committed |
|
| 2012-07-02 11:53:59 |
John Lea |
unity: status |
New |
Triaged |
|
| 2012-07-02 11:54:02 |
John Lea |
unity (Ubuntu): status |
New |
Triaged |
|
| 2012-07-02 11:54:10 |
John Lea |
unity: milestone |
|
backlog |
|
| 2012-07-02 11:54:18 |
John Lea |
unity: assignee |
|
Marco Trevisan (Treviño) (3v1n0) |
|
| 2012-07-02 11:56:21 |
John Lea |
description |
Add 'sticky edges deactivated for number of milliseconds after the user breaks the barrier' variable to CCSM. This variable would de-activate sticky edges for a set number of milliseconds every time after the user's pointer moves from one monitor to another. The idea behind this behaviour is to allow the user to course-correct after they have broken through the barrier the first time.
Don't change any of the default values for the time being; once this is implemented we will user test and experiment with different values before deciding on whether we should change the default behaviour. |
Add 'sticky edges deactivated for number of milliseconds after the user breaks the barrier' variable to CCSM. This variable would de-activate sticky edges for a set number of milliseconds every time after the user's pointer moves from one monitor to another. The idea behind this behaviour is to allow the user to course-correct after they have broken through the barrier the first time.
Don't change any of the default values for the time being; once this is implemented we will user test and experiment with different values before deciding on whether we should change the default behaviour.
Note: Before working on this bug it is worth checking with Jason Smith to see if he has already implemented some of this. |
|
| 2012-07-18 15:10:50 |
Marco Trevisan (Treviño) |
unity (Ubuntu): assignee |
|
Marco Trevisan (Treviño) (3v1n0) |
|
| 2012-07-18 15:11:00 |
Marco Trevisan (Treviño) |
unity: milestone |
backlog |
6.2 |
|
| 2012-07-18 15:11:06 |
Marco Trevisan (Treviño) |
unity: importance |
Undecided |
Low |
|
| 2012-07-18 15:11:11 |
Marco Trevisan (Treviño) |
unity: status |
Triaged |
In Progress |
|
| 2012-07-18 15:11:13 |
Marco Trevisan (Treviño) |
unity (Ubuntu): status |
Triaged |
In Progress |
|
| 2012-07-18 15:14:21 |
Marco Trevisan (Treviño) |
branch linked |
|
lp:~3v1n0/unity/barrier-timeout |
|
| 2012-07-24 23:34:39 |
Marco Trevisan (Treviño) |
unity: status |
In Progress |
Fix Committed |
|
| 2012-07-24 23:34:42 |
Marco Trevisan (Treviño) |
unity (Ubuntu): status |
In Progress |
Fix Committed |
|
| 2012-08-02 10:16:20 |
Omer Akram |
unity (Ubuntu): importance |
Undecided |
Low |
|
| 2012-08-10 12:36:23 |
Didier Roche-Tolomelli |
unity: status |
Fix Committed |
Fix Released |
|
| 2012-08-10 14:40:46 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/unity |
|
| 2012-08-13 09:24:11 |
Launchpad Janitor |
unity (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2012-09-06 09:52:39 |
John Lea |
description |
Add 'sticky edges deactivated for number of milliseconds after the user breaks the barrier' variable to CCSM. This variable would de-activate sticky edges for a set number of milliseconds every time after the user's pointer moves from one monitor to another. The idea behind this behaviour is to allow the user to course-correct after they have broken through the barrier the first time.
Don't change any of the default values for the time being; once this is implemented we will user test and experiment with different values before deciding on whether we should change the default behaviour.
Note: Before working on this bug it is worth checking with Jason Smith to see if he has already implemented some of this. |
We have tested the fix, and while it is an improvement the one of the important use cases is not yet solved. To reproduce:
1. Using a computer with two monitors, set the Launcher to auto-hide and sticky edges to 'off'
2. Set the 'sticky edges deactivated for number of milliseconds after the user breaks the barrier' variable in CCSM to "1000ms"
3. Move the pointer over the boundary from the left screen to the right screen slowly, and then try to move it back again (within 1 second).
What currently happens: the pointer gets caught on the Launcher reveal edge resistance on the left edge of the right monitor
What should happen: There should be no resistance when the pointer comes back across the barrier because the barrier was already broken inside 1000ms when the pointer moved from the left monitor to the right monitor.
Also: set the value of the variable to 1000ms
--------------------------------
Add 'sticky edges deactivated for number of milliseconds after the user breaks the barrier' variable to CCSM. This variable would de-activate sticky edges for a set number of milliseconds every time after the user's pointer moves from one monitor to another. The idea behind this behaviour is to allow the user to course-correct after they have broken through the barrier the first time.
Don't change any of the default values for the time being; once this is implemented we will user test and experiment with different values before deciding on whether we should change the default behaviour.
Note: Before working on this bug it is worth checking with Jason Smith to see if he has already implemented some of this. |
|
| 2012-09-06 09:54:22 |
John Lea |
unity (Ubuntu): status |
Fix Released |
Triaged |
|
| 2012-09-06 09:54:24 |
John Lea |
unity: status |
Fix Released |
Triaged |
|
| 2012-09-07 01:47:32 |
Marco Trevisan (Treviño) |
unity (Ubuntu): status |
Triaged |
In Progress |
|
| 2012-09-07 01:47:35 |
Marco Trevisan (Treviño) |
unity: status |
Triaged |
In Progress |
|
| 2012-09-07 01:48:14 |
Marco Trevisan (Treviño) |
branch linked |
|
lp:~3v1n0/unity/release-barrier-on-autohide |
|
| 2012-09-10 11:43:14 |
Marco Trevisan (Treviño) |
unity: status |
In Progress |
Fix Committed |
|
| 2012-09-10 11:43:17 |
Marco Trevisan (Treviño) |
unity (Ubuntu): status |
In Progress |
Fix Committed |
|
| 2012-09-10 16:48:19 |
John Lea |
description |
We have tested the fix, and while it is an improvement the one of the important use cases is not yet solved. To reproduce:
1. Using a computer with two monitors, set the Launcher to auto-hide and sticky edges to 'off'
2. Set the 'sticky edges deactivated for number of milliseconds after the user breaks the barrier' variable in CCSM to "1000ms"
3. Move the pointer over the boundary from the left screen to the right screen slowly, and then try to move it back again (within 1 second).
What currently happens: the pointer gets caught on the Launcher reveal edge resistance on the left edge of the right monitor
What should happen: There should be no resistance when the pointer comes back across the barrier because the barrier was already broken inside 1000ms when the pointer moved from the left monitor to the right monitor.
Also: set the value of the variable to 1000ms
--------------------------------
Add 'sticky edges deactivated for number of milliseconds after the user breaks the barrier' variable to CCSM. This variable would de-activate sticky edges for a set number of milliseconds every time after the user's pointer moves from one monitor to another. The idea behind this behaviour is to allow the user to course-correct after they have broken through the barrier the first time.
Don't change any of the default values for the time being; once this is implemented we will user test and experiment with different values before deciding on whether we should change the default behaviour.
Note: Before working on this bug it is worth checking with Jason Smith to see if he has already implemented some of this. |
We have tested the fix, and while it is an improvement the one of the important use cases is not yet solved. To reproduce:
1. Using a computer with two monitors, set the Launcher to auto-hide and sticky edges to 'off'
2. Set the 'sticky edges deactivated for number of milliseconds after the user breaks the barrier' variable in CCSM to "1000ms"
3. Move the pointer over the boundary from the left screen to the right screen slowly, and then try to move it back again (within 1 second).
What currently happens: the pointer gets caught on the Launcher reveal edge resistance on the left edge of the right monitor
What should happen: There should be no resistance when the pointer comes back across the barrier because the barrier was already broken inside 1000ms when the pointer moved from the left monitor to the right monitor.
Also: set the value of the variable to 1000ms
--------------------------------
Add 'sticky edges deactivated for number of milliseconds after the user breaks the barrier' variable to CCSM. This variable would de-activate sticky edges for a set number of milliseconds every time after the user's pointer moves from one monitor to another.
In addition to the 1000ms barrier switch off timer, the barrier should also only be switched off for only one crossing e.g. so that if the user tries to correct an accidental crossing of the barrier they can do so with no resistance, but after correcting this accidental crossing the barrier is switched on even if 1000ms has not yet elapsed.
The idea behind this behaviour is to allow the user to course-correct after they have broken through the barrier the first time.
Don't change any of the default values for the time being; once this is implemented we will user test and experiment with different values before deciding on whether we should change the default behaviour.
Note: Before working on this bug it is worth checking with Jason Smith to see if he has already implemented some of this. |
|
| 2012-09-19 15:37:13 |
Launchpad Janitor |
branch linked |
|
lp:~timo-jyrinki/ubuntu/quantal/unity/ubuntu.660 |
|
| 2012-09-21 05:30:46 |
Launchpad Janitor |
unity (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2012-09-21 09:11:14 |
Timo Jyrinki |
unity: status |
Fix Committed |
Fix Released |
|
| 2012-10-02 08:58:13 |
John Lea |
unity: importance |
Low |
Medium |
|
| 2012-10-02 08:58:15 |
John Lea |
unity (Ubuntu): importance |
Low |
Medium |
|
| 2012-10-08 08:56:12 |
John Lea |
unity: status |
Fix Released |
Triaged |
|
| 2012-10-08 08:56:16 |
John Lea |
unity: milestone |
6.2 |
backlog |
|
| 2012-10-08 08:56:19 |
John Lea |
unity (Ubuntu): status |
Fix Released |
Triaged |
|
| 2012-10-08 08:56:33 |
John Lea |
unity (Ubuntu): importance |
Medium |
High |
|
| 2012-10-08 08:56:36 |
John Lea |
unity: importance |
Medium |
High |
|
| 2012-10-08 08:56:49 |
John Lea |
ayatana-design: importance |
Medium |
High |
|
| 2012-10-10 10:24:02 |
John Lea |
ayatana-design: status |
Fix Committed |
Fix Released |
|
| 2012-10-10 10:24:06 |
John Lea |
unity (Ubuntu): status |
Triaged |
Fix Released |
|
| 2012-10-10 10:24:08 |
John Lea |
unity: status |
Triaged |
Fix Released |
|
| 2012-10-10 10:24:19 |
John Lea |
tags |
udp |
reviewedbydesignq |
|
