| commit | 62d62eebf11f1035bfab4c5b90c514f27c04c139 | |
| author | Roman Dobosz <gryf73@gmail.com> | |
| Tue, 21 Feb 2017 17:56:11 +0000 (21 18:56 +0100) | ||
| committer | Carlos R. Mafra <crmafra@gmail.com> | |
| Tue, 21 Feb 2017 19:24:35 +0000 (21 19:24 +0000) | ||
| tree | c41d278bb60a7539d0f4cfcc0d4f6feb1daf6745 | treesnapshot (tar.gz zip) |
| parent | 160f879cce42cfefa8afcaadbf401d1127a795ef | commitdiff |
Bugfix for moving windows between heads.
Previous bugfix introduced another regression. It fixed the issue with
size of the unmaximized window, but break new functionality. Revert back
code for maximizing using mouse, leaving out head detection for keyboard
actions, since it is already calculated.
Mouse actions for maximize also has to be fixed due to different
behaviour in original implementation - movement of the window which is
called in handleMaximize filter out MAX_KEYBOARD from argument passed to
the wMaximizeWindow, so that it will always assume that all the actions
have to be done on the head where mouse pointer resides. For moving
windows between heads feature, calculated head is always passed and
used, regardless of how maximizing was invoked (keyboard or mouse) and
mouse pointer position.
Previous bugfix introduced another regression. It fixed the issue with
size of the unmaximized window, but break new functionality. Revert back
code for maximizing using mouse, leaving out head detection for keyboard
actions, since it is already calculated.
Mouse actions for maximize also has to be fixed due to different
behaviour in original implementation - movement of the window which is
called in handleMaximize filter out MAX_KEYBOARD from argument passed to
the wMaximizeWindow, so that it will always assume that all the actions
have to be done on the head where mouse pointer resides. For moving
windows between heads feature, calculated head is always passed and
used, regardless of how maximizing was invoked (keyboard or mouse) and
mouse pointer position.
| src/actions.c | diffblobblamehistory |