Merge lp:~lukas-kde/unity8/activateWindows into lp:unity8
| Status: | Merged |
|---|---|
| Approved by: | Albert Astals Cid on 2015-11-09 |
| Approved revision: | 2035 |
| Merged at revision: | 2046 |
| Proposed branch: | lp:~lukas-kde/unity8/activateWindows |
| Merge into: | lp:unity8 |
| Prerequisite: | lp:~mzanetti/unity8/panel-button-fixes |
| Diff against target: |
709 lines (+317/-73) 7 files modified
qml/Panel/Panel.qml (+18/-1) qml/Stages/DecoratedWindow.qml (+3/-1) qml/Stages/DesktopSpread.qml (+1/-1) qml/Stages/DesktopSpreadDelegate.qml (+2/-2) qml/Stages/DesktopStage.qml (+148/-34) qml/Stages/WindowDecoration.qml (+6/-2) tests/qmltests/Stages/tst_DesktopStage.qml (+139/-32) |
| To merge this branch: | bzr merge lp:~lukas-kde/unity8/activateWindows |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Albert Astals Cid (community) | Abstain on 2015-11-09 | ||
| PS Jenkins bot | continuous-integration | 2015-10-26 | Needs Fixing on 2015-11-07 |
| Michael Zanetti (community) | 2015-10-26 | Approve on 2015-11-03 | |
| Daniel d'Andrada | 2015-10-26 | Pending | |
|
Review via email:
|
|||
This proposal supersedes a proposal from 2015-10-19.
Commit Message
Restore windows when activating from the spread, maintain a focus stack
Stop displaying the "grabbing" icon when we merely click to focus the app's decoration.
Provide keyboard shortcuts for common window operations
Description of the Change
Raise/restore windows when activating from the spread, maintain a focus stack in case we minimize/close an app.
Stop displaying the "grabbing" icon when we merely click to focus the app's decoration.
Provide keyboard shortcuts for common window operations
* Are there any related MPs required for this MP to build/function as expected? Please list.
https:/
* Did you perform an exploratory manual test run of your code change and any related functionality?
Yes
* Did you make sure that your branch does not contain spurious tags?
Yes
* If you changed the packaging (debian), did you subscribe the ubuntu-unity team to this MP?
Yes
* If you changed the UI, has there been a design review?
N/A
| Daniel d'Andrada (dandrader) wrote : | # |
| Lukáš Tinkl (lukas-kde) wrote : | # |
> Please follow the commit message format as explained here:
> https:/
Should be fine now
| Daniel d'Andrada (dandrader) wrote : | # |
Could you please add qml tests to cover those use cases you mention (ie active focus when clicking on decoration and raise/restore when activation from spread)?
I believe we already have a test for the first one (focus when clicking decoration). We had similar problems in the past before. Should investigate why it passes now even though there's a bug there (maybe it tests only with touches and not with mouse clicks, don't know).
| Daniel d'Andrada (dandrader) wrote : | # |
Oh, and it's worth making lp:~unity-team/unity8/mousePointer from silo 022 a prerequisite as it makes a lot of changes in this code.
| Daniel d'Andrada (dandrader) wrote : | # |
> > Please follow the commit message format as explained here:
> > https:/
>
> Should be fine now
Yes, thanks!
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2005
http://
Executed test runs:
UNSTABLE: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2020
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2022
http://
Executed test runs:
UNSTABLE: http://
FAILURE: http://
UNSTABLE: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
FAILURE: http://
FAILURE: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2023
http://
Executed test runs:
UNSTABLE: http://
FAILURE: http://
UNSTABLE: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
FAILURE: http://
FAILURE: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| Albert Astals Cid (aacid) wrote : | # |
are the qml failing tests a regression of this?
| Lukáš Tinkl (lukas-kde) wrote : | # |
> are the qml failing tests a regression of this?
Ah yes, most likely; gonna look into them.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2024
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
FAILURE: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2025
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
FAILURE: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| Michael Zanetti (mzanetti) wrote : | # |
file://
file://
Getting this warning frequently in the log. Please silence it.
| Lukáš Tinkl (lukas-kde) wrote : | # |
> file://
> qml:71:16: Unable to assign [undefined] to QString
> file://
> :218: TypeError: Cannot read property 'title' of null
>
> Getting this warning frequently in the log. Please silence it.
Silence, and fixed (the "model.name" was even wrong), we do get the surface name already as a fallback for window.title
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2026
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Michael Zanetti (mzanetti) wrote : | # |
Here's a case where it breaks still:
* Have only one application open (dash)
* minimize it
* press alt+tab (spread will show, dash is selected)
* release alt+tab
expected: dash restores
actual: nothing happens
* now launch something else from the launcher
expected: other app launches
actual: other app launches & dash restores
| Michael Zanetti (mzanetti) wrote : | # |
* press Ctrl+Meta+Right to half-maximize the window on the right side
* press Ctrl+Meta+Down
expected: Window restores (as it does in unity7)
actual: Window minimizes
| Michael Zanetti (mzanetti) wrote : | # |
* Minimize all windows
* Press Ctrl+Meta+Up
expected: nothing happens as there is no focused window
actual: last focused app restores
| Michael Zanetti (mzanetti) wrote : | # |
* Alt+F4 doesn't seem to work for me
* Meta+Ctrl+D to Minimize all doesn't minimize maximized and semi-maximized windows (only restored ones are minimized)
Some more inline comments too.
| Lukáš Tinkl (lukas-kde) wrote : | # |
> * Alt+F4 doesn't seem to work for me
> * Meta+Ctrl+D to Minimize all doesn't minimize maximized and semi-maximized
> windows (only restored ones are minimized)
>
> Some more inline comments too.
All issues hopefully fixed; found a new one: we should restore minimized apps to their previous state (not normal) respecting the maximized bits.
Please test again :)
| Michael Zanetti (mzanetti) wrote : | # |
Quite an improvement, yes! Still some small ones.
* minimize a maximized window, select it in the spread => expected: maximized, actual: restored. Same for closing a maximized one and reopening. Not sure how far we want to go with those in a single branch... this one improves things already a lot and there's still lots to do. So you decide when you want to give it a rest with this branch. We can start splitting things into multiple branches.
* managed to break alt+f4 again. I tried to log out and in again and break it again but didn't manage so far. Will keep on trying.
* During the above, I found a super weird one :D Minimize all windows, now ctrl+meta+arrow shouldn't do anything any more. Here's how: press and hold ctrl+meta and then press all 4 arrows dogether down two times in a row. It will restore a window :D Not that this would be a common thing to do, but it does indicate some focus issue when everything is minimized. Can you try to find out what's going on?
- ApplicationMana
+ ApplicationMana
careful with that... can you explain the reason for this? The difference is that with "requestFocusAp
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2027
http://
Executed test runs:
UNSTABLE: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2028
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
UNSTABLE: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Lukáš Tinkl (lukas-kde) wrote : | # |
All issues fixed, wasn't able to reproduce the Alt+F4 problem, neither the ctrl+meta+arrows one.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2029
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Michael Zanetti (mzanetti) wrote : | # |
> All issues fixed, wasn't able to reproduce the Alt+F4 problem, neither the
> ctrl+meta+arrows one.
the ctr+meta-arrows is really easy to reproduce tho... just minimize all whindows, press and hold ctrl and alt, then use your flat hand to press down all the arrow keys, twice in a row. It will restore some windows.
Just found another one: when you semi-maximize a window (left or right), it is placed below the panel, but the panel's height is not subtracted and so the window's bottom edge is outside the screen.
| Michael Zanetti (mzanetti) wrote : | # |
I think I found how to reproduce the lost alt+f4: Switch to another vt (e.g. the unity7 session) and back to unity8. Alt+F4 will be gone. Could be an issue with general input handling and not directly related to the branch... Please give it a quick look if it is to be fixed in here or not.
| Lukáš Tinkl (lukas-kde) wrote : | # |
> > All issues fixed, wasn't able to reproduce the Alt+F4 problem, neither the
> > ctrl+meta+arrows one.
>
> the ctr+meta-arrows is really easy to reproduce tho... just minimize all
> whindows, press and hold ctrl and alt, then use your flat hand to press down
> all the arrow keys, twice in a row. It will restore some windows.
Can't reproduce at all :/ Nothing happens in this case
>
> Just found another one: when you semi-maximize a window (left or right), it is
> placed below the panel, but the panel's height is not subtracted and so the
> window's bottom edge is outside the screen.
Thanks for spotting, fixed
| Lukáš Tinkl (lukas-kde) wrote : | # |
For reference, the Alt+F4 bug seems to be caused by:
https:/
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2030
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Michael Zanetti (mzanetti) wrote : | # |
all issues addressed now.
* Did you perform an exploratory manual test run of the code change and any related functionality?
yes
* Did CI run pass? If not, please explain why.
it did for vivid, at least qmltests. AP tests seem to have issues flashing devices.
* Did you make sure that the branch does not contain spurious tags?
yes
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2031
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Albert Astals Cid (aacid) wrote : | # |
Note: was already top approved
Text conflict in qml/Panel/Panel.qml
Text conflict in qml/Stages/
Text conflict in tests/qmltests/
3 conflicts encountered.
- 2033. By Lukáš Tinkl on 2015-11-06
-
merge trunk
- 2034. By Lukáš Tinkl on 2015-11-06
-
cleanup
- 2035. By Lukáš Tinkl on 2015-11-06
-
cleanup
| Lukáš Tinkl (lukas-kde) wrote : | # |
Conflicts resolved
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2032
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2035
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Albert Astals Cid (aacid) wrote : | # |
Top approving again now that merge has made CI happy.

Please follow the commit message format as explained here: https:/ /wiki.ubuntu. com/Process/ Merges/ Checklists/ Unity8