Unity

Merge lp://qastaging/~gordallott/unity/lock-out-hud into lp://qastaging/unity

lock-out-hud
Merge into trunk

Proposed by Gord Allott on 2012-03-16

Status:

Superseded

Proposed branch:

lp://qastaging/~gordallott/unity/lock-out-hud

Merge into:

lp://qastaging/unity

Diff against target:

661 lines (+323/-57)

14 files modified

manual-tests/Hud.txt (+13/-0)
plugins/unityshell/src/BFBLauncherIcon.cpp (+19/-0)
plugins/unityshell/src/BFBLauncherIcon.h (+1/-0)
plugins/unityshell/src/HudController.cpp (+33/-11)
plugins/unityshell/src/HudController.h (+4/-0)
plugins/unityshell/src/HudLauncherIcon.cpp (+115/-0)
plugins/unityshell/src/HudLauncherIcon.h (+56/-0)
plugins/unityshell/src/HudView.cpp (+27/-6)
plugins/unityshell/src/HudView.h (+10/-1)
plugins/unityshell/src/Launcher.cpp (+26/-32)
plugins/unityshell/src/LauncherController.cpp (+2/-0)
plugins/unityshell/src/LauncherHideMachine.cpp (+7/-7)
plugins/unityshell/src/UBusMessages.h (+5/-0)
plugins/unityshell/src/unityshell.cpp (+5/-0)

To merge this branch:

bzr merge lp://qastaging/~gordallott/unity/lock-out-hud

High

Fix Released

Link a bug report

Reviewer	Date Requested	Status
Marco Trevisan (Treviño)		Needs Fixing on 2012-03-20
Mirco Müller	2012-03-16	Pending
Review via email: mp+97831@code.qastaging.launchpad.net

This proposal has been superseded by a proposal from 2012-03-21.

Description of the change

Changes the behaviour of the HUD/Launcher interaction in HideMode: Never

= The Problem =
See: https://bugs.launchpad.net/ayatana-design/+bug/921506

= The Fix =
Modify the Launcher to accept a new LauncherIcon that will listen to a UBUS message dictating its icon

= Testing =
Manual test included, lock-out behaviour is not included in out AP tests so ensuring a valid AP test seems non trivial at this point, requires an AP test module that can modify compiz options

Revision history for this message

Tim Penhey (thumper) wrote on 2012-03-19:

Actually adding an autopilot test for this is trivial.

What we can do is to run the HUD AP tests with the launcher in each state, locked out and auto-hide. We already do something like this for launchers for each monitor. I'll tackle the HUD tests with thomi tomorrow.

Revision history for this message

Didier Roche-Tolomelli (didrocks) wrote on 2012-03-20:

we want that for this release isn't it? can someone review it and merge it with the manual test if anyone has the AP test for it?

Revision history for this message

Marco Trevisan (Treviño) (3v1n0) wrote on 2012-03-20:

This has some conflicts with trunk, also you're using some lambda functions to connect to sigc::signal's, but in that case you need to disconnect from them in destructor or use a sigc::mem_fun instead (this doesn't apply to the ubus callback functions, of course).

Plus, I'm not sure if that's wanted, but if enabling the launcher's audohide feature, when closing the HUD, the launcher reveals and then closes again.

42 + if (!g_strcmp0(overlay_identity, "hud"))

Why not using overlay_identity.Str() == "hud" ?

launcher_width.changed.connect([this] (int new_width) { Relayout(); });

I guess you can just pass [&] and please follow what said above. Even if the hud view shouldn't be destroyed, I guess it's better to stay safe.

review: Needs Fixing

Revision history for this message

Tim Penhey (thumper) wrote on 2012-03-21:

As well as the launcher popping out when you close the hud, if you do the following:
press Alt
press Super

You get the dash with a hidden launcher.

Also, you get a peaking icon when you start the hud with a hidden launcher.

I'm fixing these now. I have a branch that fixes everything so far except making sure the icon saturation is right at the right time.

Revision history for this message