Add support for middle mouse button emulation
ClosedPublic

Authored by strobach on Oct 28 2016, 11:34 AM.

Details

Reviewers
graesslin

Diff Detail

Repository
R108 KWin
Lint
Lint Skipped
Unit
Unit Tests Skipped
strobach updated this revision to Diff 7718.Oct 28 2016, 11:34 AM
strobach retitled this revision from to Add support for middle mouse button emulation.
strobach updated this object.
strobach edited the test plan for this revision. (Show Details)
strobach set the repository for this revision to R108 KWin.
strobach added a project: KWin.
Restricted Application added a subscriber: kwin. ยท View Herald TranscriptOct 28 2016, 11:34 AM
graesslin accepted this revision.Oct 28 2016, 1:10 PM
graesslin added a reviewer: graesslin.
graesslin added a subscriber: graesslin.

Thanks a lot. I'm really surprised that we didn't have that one exposed yet. I just checked whether it wasn't available in 1.2 and got added later on, but no, it's already in 1.2. I must have overread that one in the documentation...

If you want you could also extend the autotests/libinput/device_test.cpp by a simple test case to verify that it works correctly. After all you already implemented the mocking ;-)

This revision is now accepted and ready to land.Oct 28 2016, 1:10 PM
strobach closed this revision.Oct 31 2016, 6:38 PM

Thanks for the review. Can you please land the diff for me?

graesslin reopened this revision.Nov 2 2016, 8:20 AM
This revision is now accepted and ready to land.Nov 2 2016, 8:20 AM

Thanks for the review. Can you please land the diff for me?

Given the number of reviews you have: do you want to apply for a git account? See https://community.kde.org/Infrastructure/Get_a_Developer_Account

Given the number of reviews you have: do you want to apply for a git account? See https://community.kde.org/Infrastructure/Get_a_Developer_Account

I did (https://identity.kde.org/index.php?r=developerApplication/view&id=637).
How to proceed once (if) the application is approved? Since I haven't used Arcanist to create the diff, will it be enough to use "Differential Revision:" keyword in the commit to pair it with the respective diff? Do I understand it right, that there's no mechanism ensuring that what I'm committing is what was under review?

How to proceed once (if) the application is approved? Since I haven't used Arcanist to create the diff, will it be enough to use "Differential Revision:" keyword in the commit to pair it with the respective diff? Do I understand it right, that there's no mechanism ensuring that what I'm committing is what was under review?

Yes it's enough to use the Differential Revision and it will be picked up when pushing. And yes there is no mechanism ensuring that what you are committing is what was under review. KDE puts a great deal of trust in its contributors. As a matter of fact code review is actually non-mandatory. If you look at the commit history you'll see quite a lot commits by me not going through the reviews - especially if I add autotests.

As that change was for a bug report you can auto-close it by using the
BUG: 123456

keyword. And in addition you can specify a:
FIXED-IN: 5.8.4

And that also shows: please push to Plasma/5.8 branch :-)

Thanks for the explanation.

And that also shows: please push to Plasma/5.8 branch :-)

Do you mean only to Plasma/5.8 and you're going to merge into master later?

Thanks for the explanation.

And that also shows: please push to Plasma/5.8 branch :-)

Do you mean only to Plasma/5.8 and you're going to merge into master later?

yes, I can do the merge. I regularly merge anyway when I push changes)

Thanks for the explanation.

And that also shows: please push to Plasma/5.8 branch :-)

Do you mean only to Plasma/5.8 and you're going to merge into master later?

yes, I can do the merge. I regularly merge anyway when I push changes)

OK. Thanks again.

strobach closed this revision.Nov 3 2016, 1:10 PM