-
Notifications
You must be signed in to change notification settings - Fork 28
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
20 additions
and
21 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
a1e92d7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Goshin: this commit produces some issues with my trackpad (when I have to select or drag something while keeping one finger in a corner of touchpad and moving another finger to select a long block or move something in a long distance, so I have to up this finger and touch again):
https://drive.google.com/file/d/1MVhIQeI9FnlSoNIh6JgycrYrjfeX-Tyq/view?usp=sharing
https://drive.google.com/file/d/18VfySvw5-c0MlNUIJ9d7tqWdsLa_rTjz/view?usp=sharing
https://drive.google.com/file/d/1_ymIW6C8upa2Z7g9nx113XTNPVbIeJEz/view?usp=sharing
a1e92d7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lvs1974 are you sure there is any functional change in this commit? It looked like plain refactoring to me. Better make an issue…
a1e92d7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@vit9696: it is not just a plain refactoring...
is not the same as:
input_active |= transducer->isTransducerActive;
a1e92d7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lvs1974 When would the cursor jump happen? When you release or re-contact the second finger?
a1e92d7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Goshin: Cursor jumps when I re-contact the second finger.
a1e92d7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lvs1974 as discussed in #10, this is really a device-specific problem. From the log file you gave in #10 (comment), the states are messed up when you do the gesture.
isTransducerActive
of the first finger wrongly becomes false, andisTransducerActive
for the second finger wrongly remains true when the second finger leaves.and the position of the first finger drifts when the second finger re-contact.
You can try the workaround here, like before to temporarily ignore the first finger in this case.
This is ugly and now I kind of wonder if it should be solved in VoodooInput because it is intended to be a generic MT2 adapter while this is a device problem.
In VoodooI2C/VoodooI2C#445 they are going to handle button clicks via the other
TrackpointDevice
IOHIPointing device, and consider removing theisPhysicalButtonDown
field. Afterward maybe this problem will be solved automatically.a1e92d7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Goshin: I have tried a workaround, but unfortunately it did not fix this issue.
I totally agree it is a device-specific problem.
Probably it will be fixed with VoodooI2C/VoodooI2CHID#39.
a1e92d7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Goshin: I built a VoodooI2C & VoodooI2CHID from https://github.com/usr-sse2/VoodooI2C (branch for PR VoodooI2C/VoodooI2C#445) and used the latest VoodooInput from acidanthera master (without workaround you suggested today).
And it works so far!