System ignores mouse REL events.
Bug #570135 reported by
Raumkraut
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Pystromo |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
When a mouse device is captured by Pystromo, even if no remapping takes place, outputted/
The very first mouse motion appears to work (the mouse moves ever so slightly - once), but further motion has no effect.
The REL events are seen by Pystromo, and are successfully passed through to the `uinput` device node.
Running `cat /dev/input/mice` while Pystromo is in operation shows that the events also successfully make their way to that point.
More research is required, and hopefully a blast of inspiration.
Q. Perhaps it's being seen by X as not coming from a/the 'core pointer device'?
Q. Perhaps `xev` can shed some light on the difference?
| Changed in pystromo: | |
| status: | New → Confirmed |
Revision history for this message
| Daninator (daniel-rade) wrote | #1 |
To post a comment you must log in.
Hello, I have done some checks on this problem using a N52te:
- I configured D-PAD with mouse axis: X takes motion into account without pystromo
- when using pystromo to send REL_event, whatever the button `xev` detects the REL event but mouse coordinates aren't updated so X consider it had to move the pointer at the same position. It seems the event.value content isn't taken into account