Fix the order of arguments passed to changeMaximize method
ClosedPublic

Authored by zzag on Mon, Nov 18, 12:34 PM.

Details

Summary

BUG: 413424
BUG: 412888
BUG: 413554
FIXED-IN: 5.17.4

Diff Detail

Repository
R108 KWin
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
zzag created this revision.Mon, Nov 18, 12:34 PM
Restricted Application added a project: KWin. · View Herald TranscriptMon, Nov 18, 12:34 PM
Restricted Application added a subscriber: kwin. · View Herald Transcript
zzag requested review of this revision.Mon, Nov 18, 12:34 PM
zzag edited the summary of this revision. (Show Details)Mon, Nov 18, 12:41 PM
davidedmundson accepted this revision.Mon, Nov 18, 12:50 PM
davidedmundson added a subscriber: davidedmundson.

Urgh, I'm sure this is the second case I've seen of this at least.

Lets maybe add a changeMaximise(Qt::Orientations) overload and phase this out.

This revision is now accepted and ready to land.Mon, Nov 18, 12:50 PM
zzag added a comment.EditedMon, Nov 18, 1:08 PM

Urgh, I'm sure this is the second case I've seen of this at least.

Yeah, the first case was about the wrong order of parameters in Client::changeMaximize.

EDIT: It was Client not ShellClient.

Lets maybe add a changeMaximise(Qt::Orientations) overload and phase this out.

Do you want me to do it in this revision or another one?

zzag edited the summary of this revision. (Show Details)Mon, Nov 18, 1:46 PM

Later is fine, there's no rush.

This revision was automatically updated to reflect the committed changes.