From 3475bfb2aa832e238a293f58d533c64e2ddfd4aa Mon Sep 17 00:00:00 2001 From: Jeff Young Date: Tue, 13 Aug 2019 09:58:54 +0100 Subject: [PATCH] New move tool doesn't require GetAndPlace to jump through hoops. And at least one of those hoops leaves the cursor forced. Fixes: lp:1839877 * https://bugs.launchpad.net/kicad/+bug/1839877 (cherry picked from commit dd938b02df435853340b130f1dcaaf8d6b9c7182) --- pcbnew/tools/selection_tool.cpp | 7 ------- 1 file changed, 7 deletions(-) diff --git a/pcbnew/tools/selection_tool.cpp b/pcbnew/tools/selection_tool.cpp index 83147499a3..6efd0e54b8 100644 --- a/pcbnew/tools/selection_tool.cpp +++ b/pcbnew/tools/selection_tool.cpp @@ -1284,15 +1284,8 @@ int SELECTION_TOOL::findMove( const TOOL_EVENT& aEvent ) // cursor before waiting for mouse move events m_selection.SetReferencePoint( module->GetPosition() ); - // Place event on module origin first, so the generic anchor snap - // doesn't just choose the closest pin for us - viewCtrls->ForceCursorPosition( true, module->GetPosition() ); - // pick the component up and start moving m_toolMgr->RunAction( PCB_ACTIONS::move, true ); - - // restore the previous cursor position - viewCtrls->SetCursorPosition( cursorPosition, false ); } return 0;