Merge lp:~azzar1/unity/properly-handle-copy-dialog into lp:unity
Proposed by
Andrea Azzarone
Status: | Merged |
---|---|
Approved by: | Marco Trevisan (Treviño) |
Approved revision: | no longer in the source branch. |
Merged at revision: | 4202 |
Proposed branch: | lp:~azzar1/unity/properly-handle-copy-dialog |
Merge into: | lp:unity |
Prerequisite: | lp:~azzar1/unity/fix-blinking-fm-icon |
Diff against target: |
351 lines (+248/-12) 5 files modified
launcher/FileManagerLauncherIcon.cpp (+30/-0) launcher/FileManagerLauncherIcon.h (+8/-0) launcher/StorageLauncherIcon.cpp (+7/-12) tests/CMakeLists.txt (+1/-0) tests/test_file_manager_launcher_icon.cpp (+202/-0) |
To merge this branch: | bzr merge lp:~azzar1/unity/properly-handle-copy-dialog |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Marco Trevisan (Treviño) | Approve | ||
PS Jenkins bot | continuous-integration | Pending | |
Review via email: mp+299301@code.launchpad.net |
Commit message
Properly handle the file manager copy dialog in FileManagerLaun
To post a comment you must log in.
Sorry for being late, but... Yeah, although I'd like to get rid of that WindowManager: :Default( ).IsWindowMappe d(app_win- >window_ id()) check, I know that there are multiple races involved there, so we can't probably avoid it.
Just wondering if it could happen that the mapping would happen afterwards and we'd miss a window because there's no other signal catching that (and compiz might not signal us anything)...
But things work ok with this, so let's put it in production.