Bug: Switching to the Hand tool too fast causes timeline to jump

Si, el problema ya viene de hace tiempo , trabajando con el ratón se hace imprescidible usar este herramienta para moverse en la linea de tiempo sin tener que estar haciendo zoom constantemente , dejando la H pulsada se activa muy rápido y no te obliga a cambiar de herramienta principal, que suele ser A , de modo que puedes seleccionar y desplazarte muy rápido por la linea de tiempo .

Con trackpad no es necesario , claro . No tengo un ratón con esfera solo con rueda Up y Down , por lo que el desplazamiento horizontal no es posible. De cualquier modo es un Bug que antes no existía y desde hace ya unas versiones que llevamos arrastrando . Había contestado a ese hilo , pero ya he mandado el feedback a Apple , aqui : Feedback - Final Cut Pro - Apple sería de gran ayuda si más nos sumáramos reportando este bug a Apple . Gracias

excuse me , yes it was a reply to other thread :

reply to : Using a hotkey to switch to the Hand tool to move the timeline, and then immediately left-clicking the timeline to move it with the Hand tool, causes the timeline to jump erratically to the left. Seemingly, when using a hotkey to switch to the Hand tool, there is a brief window after pressing the hotkey during which interacting with the timeline with the Hand causes the timeline to jump abruptly away from you.

Edit additional testing - it seems to be caused by holding the Hand tool hotkey and left-clicking the timeline and moving the mouse, which for some reason tries to drag the view to the start of the timeline.

Reproduce: hold the Hand tool hotkey (for instance H), then hold the left-click on the timeline which causes the Hand cursor to grab, and then move the mouse in any direction to gently drag. This will cause the timeline view to shoot to the start of the timeline, while also fighting to move in the direction you are trying to drag it.

Having used FCP for years this has only started happening recently. Tried with different keyboards, different mice, and after rebooting, problem still persists. Currently having to edit at a more hunt-and-peck pace to get around this bug.