Mouse movement delay

Software
1

Hi

Ask questions using a translator.

I recently installed KICAD on my new laptop.
It is version 5.1.6 and is 64-bit.
This phenomenon also occurs in the lower version and the same occurs in the 686 version.

Symptoms are identified as follows.

  1. PCB design screen
  2. Select a part
  3. Use the’M’ key to execute the move
  4. Move the mouse in a circle.
  5. It shows breaking phenomenon, and parts do not move naturally.

Another next phenomenon

  1. Press the middle mouse button.
  2. Drag the entire screen.
  3. It moves while the screen is cut off.

I checked with all the mice I have.

  1. The phenomenon does not appear in the MS Bluetooth mouse.
  2. The latest wired Gamming Mouse all show the same symptoms.
  3. The 20-year-old Logitech USB mouse doesn’t work.

So, the USB mouse read the descriptor and confirmed it.
A gaming mouse transmits 16-bit moving data and has a maximum movement value of ±32768.
A 20 year old mouse is ±128.

Any mouse you have can move and drag the window normally, and it will work without problems with other cads.

Only KICAD causes problems with today’s new laptops.
It had nothing to do with the graphics card. AMD’s Integrated Graphics Or Nvidia Graphics
Thank you for checking.

My laptop is a specification.
Lenovo LEGION 5 15ARH R5 ZEN PRO
AMD 4600H CPU
Win10 Pro

Thank you.

2

Is it this problem? https://gitlab.com/kicad/code/kicad/-/issues/4741

3

Could you make a movie of the issue? I’m not sure it’s 100% related to the issue @eelik’s talking about.
Tom

4

Similar or the same.
A video similar to me seems to have been posted.
The same goes for the lowest DPI setting on the gaming mouse.

  1. Gamming Mouse A (±32768) : Screen Moving Skip
  2. Gamming Mouse B (±32768) : Screen Moving Skip
  3. MS Sculpt Comfort Bluetooth Mouse : Ok
  4. Very Old Logitech USB Mouse (±127) : OK
  5. Logitech Low cost wireless Mouse (±127) : OK

This is the result of simultaneous test by connecting 4 mice at the same time.
The mouse event of the window is not generated for each mouse, and the app cannot create a separate event, so it appears as a moving coordinate error after handling the event.
If you move the mouse with ±32768 very slowly, it seems to move without any problems since it is within the ±128 range.

8

Leveled up. See if you can post now.

10

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.