(Actually this also happens to me in eeschema, but I had to chose a category…)
I’m on OpenSUSE Tumbleweed, using kicad 5.1.4. The problem I’m describing has however been there for me with previous versions of kicad 5 as well, not sure when it started.
It does not happen on another machine running kubuntu 18.04 with kicad 5.1.3 (in a VM actually).
As soon as I start moving an item, cursor plus item jump close to the top left window corner, and the screen starts scrolling quite quickly. This strange behavior does not appear to depend on choice of tool set or acceleration settings. It also does not depend on whether ‘center and warp cursor on zoom’ is enabled or not. Disabling ‘pan while moving object’ makes this a little less annoying obviously.
OpenSUSE is not officially supported so it could simply be a platform specific problem. Could you update your kicad version on ubuntu to the same as in SUSE and check if you have the same behaviour as in SUSE (then it would be something with your setup instead of something with SUSE)
hi jos,
good idea, however the mouse is a wired one so no chance here
(Actually, in general a mouse click does not cause any cursor jumps, neither in kicad nor in any other place - I guess that sort of rules out misbehavior of the mouse hardware)
hi Rene,
I’ll do so once 5.14 is available from the ppa I’m using for kubuntu.
However, on my Tumbleweed machine, the strange behavior certainly was there with earlier versions of kicad, so I do not have too much hope that I could reproduce the issue on kubuntu with 5.1.4.
I may not have stated it clearly in my initial post, but the kubuntu installation is actually on a different PC, where it runs in a VM.
I just did a test with a different mouse (an old MS optical mouse) on my tumbleweed system - the problem does not appear with this mouse.
One thing special with “problem-mouse” (a CSL E.VO ergonomic one) is that I use a ‘coordinate transformation matrix’ (https://wiki.ubuntu.com/X/InputCoordinateTransformation) to adapt mouse speed between wacom tablet and ergo mouse. I’ll do a test if this mouse movement scaling is actually causing problems for kicad.
update: I disabled the transformation matrix, and the problem is gone (however the mouse way too fast). So it seems something special happens in kicad if a non-unity coordinate transformation matrix is in place for the mouse.
They actually do, the wireless ones. If the battery reaches a critical low level then data sent by a mouse can be erratic. This does not just affect KiCad, rather the entire system.
