Merge lp:~andreas-pokorny/mir/alternative-fix-1522673 into lp:mir
Status: | Superseded |
---|---|
Proposed branch: | lp:~andreas-pokorny/mir/alternative-fix-1522673 |
Merge into: | lp:mir |
Diff against target: |
167 lines (+87/-11) 4 files modified
src/platforms/evdev/libinput_device.cpp (+28/-8) tests/include/mir/test/doubles/mock_libinput.h (+2/-0) tests/mir_test_doubles/mock_libinput.cpp (+10/-0) tests/unit-tests/input/evdev/test_libinput_device.cpp (+47/-3) |
To merge this branch: | bzr merge lp:~andreas-pokorny/mir/alternative-fix-1522673 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
PS Jenkins bot (community) | continuous-integration | Approve | |
Alan Griffiths | Needs Information | ||
Review via email:
|
This proposal has been superseded by a proposal from 2015-12-07.
Commit message
Adjusts how the scroll axis are interpreted and changes the positive direction of scroll values
Instead of ticks (that do not map well for touchpad based scrolling) scroll units of libinput are used as reference. Hence button events in X11 platform are scaled now too. Evdev platform now uses the same positive scroll direction as android-input: 'up'-'right'.
Description of the change
This is an alternative fix, described here as last option
https:/
So with libinput, instead of using device dependent ticks, we are using scroll units that may be affected by device specific settings. Thus have a better chance to be normalized. This is the reason why the values differ compared to andoird-input. A change was also made in in qtmir to no longer scale the values reported by mir.
Changing the meaning of mir_pointer_ event_axis_ value() is surely an API break?
Do we really know the effect on all downstreams?