Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Visually inconsistent behaviour when drawing with 2 pointing devices attached to the same keyboard, i.e. trigger key #29

Closed
bk138 opened this issue Oct 8, 2016 · 9 comments
Assignees

Comments

@bk138
Copy link
Owner

bk138 commented Oct 8, 2016

No description provided.

@bk138 bk138 added the bug label Oct 8, 2016
@bk138 bk138 self-assigned this Oct 8, 2016
@bk138
Copy link
Owner Author

bk138 commented Oct 8, 2016

bildschirmfoto von 2016-10-08 14 16 14

drawing U-shaped arcs results in that

@bk138
Copy link
Owner Author

bk138 commented Oct 8, 2016

Ha, this stems from two pointing devices on my Thinkpad being connected to the same set of buttons. Mhh, and now?

@bk138 bk138 removed the bug label Oct 8, 2016
@bk138 bk138 changed the title Line drawing broken: always adds a straight line connecting start and end point Visually inconsistent behaviour when drawing with 2 pointing devices attached to the same keyboard, i.e. trigger key Oct 8, 2016
@russel
Copy link
Contributor

russel commented Nov 22, 2016

I can report that on a Lenovo X1, with Wacom Tablet, Logitech USB mouse, ELAN Touchscreen, TPPS/2 IBM Trackpoint and SynPS/2 Synaptics Touchpad then when using the mouse, touchpad or touch screen I get a line from the previous end point to the new start point and then a line from the new end point to the new start point. Sadly this makes the mouse, touchpad and touchscreen unusable as input devices. The same problem does not happen using the trackpoint or a Wacom tablet. Removing the mouse and the tablet makes no difference, so it must be the built in combination that is problematic. I think this is just confirming the problem.

@vonpupp
Copy link

vonpupp commented Feb 11, 2018

I confirm this issue also on a Lenovo X230 also. I get the following after I start the program:

Could not open /home/av/.config/gromit-mpx.cfg: No such file or directory
Could not open /etc/gromit-mpx/gromit-mpx.cfg: No such file or directory
Supported backends: x11 wayland 
Using backend: x11
Enabled Device 0: "Virtual core pointer", (Type: 0)
Enabled Device 1: "TPPS/2 IBM TrackPoint", (Type: 7)
Enabled Device 2: "SynPS/2 Synaptics TouchPad", (Type: 6)
Enabled Device 3: "Virtual core XTEST pointer", (Type: 0)
Now 4 enabled devices.

(gromit-mpx:9009): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

I am using Awesome WM without composite on Arch Linux. Any idea?

Thanks.

@bk138
Copy link
Owner Author

bk138 commented Feb 11, 2018

See above.

two pointing devices on my Thinkpad being connected to the same set of buttons.

@vonpupp
Copy link

vonpupp commented Feb 11, 2018

Sorry but I just installed gromit-mpx and I am not familiarized with it yet.

Could you please elaborate on how to blacklist the other devices on gromit-mpx? Is there a way to achieve this on the config file? I haven't found this on the example.

I don't have external devices connected to the notebook, I am not sure why it recognizes 4 devices.

Thanks.

@bk138
Copy link
Owner Author

bk138 commented Feb 12, 2018

You see the devices built into your machine. Maybe setting master/slaves via https://linux.die.net/man/1/xinput helps.

@vonpupp
Copy link

vonpupp commented Feb 12, 2018

Hi, thank you for your help.

Here is the output of xinput:

> $ xinput                                                                                                                                                               
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPad              	id=11	[slave  pointer  (2)]
⎜   ↳ TPPS/2 IBM TrackPoint                   	id=12	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Video Bus                               	id=7	[slave  keyboard (3)]
    ↳ Sleep Button                            	id=8	[slave  keyboard (3)]
    ↳ Integrated Camera: Integrated C         	id=9	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=10	[slave  keyboard (3)]
    ↳ ThinkPad Extra Buttons                  	id=13	[slave  keyboard (3)]

When I disable id=11 only, I cannot move the pointer. When I disable id=12 only, I cannot click. Any other idea?

@bk138
Copy link
Owner Author

bk138 commented Nov 4, 2018

Works before 58bdef4

bk138 pushed a commit that referenced this issue Dec 28, 2018
This is a rework of 58bdef4 and closes #29.
@bk138 bk138 closed this as completed in cc3c090 Dec 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants