Unity

Launcher should not be locked in place until the pointer is actually in the corner

Bug #706146 reported by Mark Shuttleworth on 2011-01-22

This bug affects 2 people

	Status	Importance	Assigned to	Milestone
Unity	Fix Released	High	Didier Roche-Tolomelli	Unity 3.4.4
unity-2d	Invalid	Medium	Unassigned
unity (Ubuntu)	Fix Released	Undecided	Unassigned
unity-2d (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

When revealing the launcher through the hot corner, the launcher should proximity-fade in as the pointer crosses the Ubuntu button, but it should also fade out if the pointer starts moving AWAY from the corner without actually hitting it first.

The specification gives an algorithm for launcher opacity based on the proximity of the pointer to the corner, however that should be tweaked to start at 50% at the edge and move to 100% in the corner (I will update the spec if requested but the math should be clear ;-)).

When the pointer hits the corner, the launcher should be sticky so the pointer can then be moved down onto the actual icon desired. In addition, if the launcher is folded, it should not unfold instantly when the mouse is coming down from the top corner, it should wait till we have some idea where the user is going and unfold *there*, to make it easier to hit the right app at the bottom of a very folded launcher.

Related branches

lp:~didrocks/unity/add-proximity-effect-706146

Merged into lp:unity at revision 862

Jason Smith (community): Approve on 2011-02-16

lp:ubuntu/natty/unity

Mark Shuttleworth (sabdfl) on 2011-01-22

Changed in unity:
importance:	Undecided → High

Revision history for this message

David Barth (dbarth) wrote on 2011-01-24:

Jason, please refer to the "Unity Launcher changes for Desktop adoption in 11.04" document

Changed in unity:
assignee:	nobody → Jason Smith (jassmith)
milestone:	none → 3.4

David Barth (dbarth) on 2011-01-24

Changed in unity:
status:	New → Triaged

Neil J. Patel (njpatel) on 2011-02-07

Changed in unity:
milestone:	3.4 → 3.4.2

David Barth (dbarth) on 2011-02-07

Changed in unity:
milestone:	3.4.2 → 3.6

Florian Boucault (fboucault) on 2011-02-08

Changed in unity-2d:
status:	New → Triaged
importance:	Undecided → High

Didier Roche-Tolomelli (didrocks) on 2011-02-10

Changed in unity:
assignee:	Jason Smith (jassmith) → Didier Roche (didrocks)

Revision history for this message

Didier Roche-Tolomelli (didrocks) wrote on 2011-02-16:

So, it's now merged and we can fade on proximity in the bfb.

FYI, I tweaked the value from 50% to ~35% for the initial state as I found it a little "bumpy" otherwise. Tell me what you think about it.

I think also that we should be maybe a little bit more flexible (maybe 5%?) in the future for the "lock" state as we can miss it if we are going too quick.

The "unfold" part will came later separately.

Changed in unity:
status:	Triaged → Fix Committed
milestone:	3.6 → 3.4.4

Revision history for this message

David Callé (davidc3) wrote on 2011-02-17:

Actually, the implemented corner lock induces a lot of hit and miss for me. The movement to open the launcher seemed more fluid and somewhat more "organic" when you didn't have to stuck the pointer in the corner before going down.

Revision history for this message

Doug McMahon (mc3man) wrote on 2011-02-17:

Seems here to not be having the intended 'fix', exception being Active Dodge'
filed Bug #721003

Didier Roche-Tolomelli (didrocks) on 2011-02-18

Changed in unity:
status:	Fix Committed → Fix Released

Florian Boucault (fboucault) on 2011-02-21

Changed in unity-2d:
milestone:	none → 3.8

Revision history for this message

Doug McMahon (mc3man) wrote on 2011-02-27:

Since the last unity(3d) upgrade there have been random mis-behaviors of the launcher when in any of the 3 autohide modes that may be related to this 'feature'
Included are -
trigger/lock point becomes non effective, the launcher is not exposed
lock point becomes non effective, launcher exposes but can't be locked
at login launcher fluctuates between hidden and exposed, no control

Or maybe they're caused by something else - the first 2 can usually be 'fixed' by opening/closing dash, 3rd requires restart

Florian Boucault (fboucault) on 2011-03-02

Changed in unity-2d:
milestone:	3.8 → none
importance:	High → Medium

Didier Roche-Tolomelli (didrocks) on 2011-05-31

Changed in unity-2d (Ubuntu):
status:	New → Triaged

Florian Boucault (fboucault) on 2011-09-20

Changed in unity-2d:
status:	Triaged → Invalid
Changed in unity-2d (Ubuntu):
status:	Triaged → Invalid

Marco Trevisan (Treviño) (3v1n0) on 2014-07-25

Changed in unity (Ubuntu):
status:	New → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.