| broulik | |
| davidedmundson |
| KWin | |
| Plasma |
On X11 modifier+mouse button on the window decoration triggers the
"special" handling thus as unrestricted move instead of passing the click
to the decoration. Of course on Wayland we want to have the same
functionality.
BUG: 386708
FIXED-IN: 5.11.4
New test case added. PointerInputTest still passes.
| Automatic diff as part of commit; lint not applicable. |
| Automatic diff as part of commit; unit tests not applicable. |
ship it, but I have a question
| input.cpp | ||
|---|---|---|
| 960 | if we're always going to do: if (actionResult.first) {
return actionResult.second;why return two bools and not just "and" them here? | |
| input.cpp | ||
|---|---|---|
| 960 | if actionResult.first is true we should not further process and return the result of actionResult.second. If actionResult.second is false we don't know anymore what the result of actionResult.first was if we and them. | |