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 dd938b02df
)
This commit is contained in:
parent
f9f8fade89
commit
3475bfb2aa
|
@ -1284,15 +1284,8 @@ int SELECTION_TOOL::findMove( const TOOL_EVENT& aEvent )
|
||||||
// cursor before waiting for mouse move events
|
// cursor before waiting for mouse move events
|
||||||
m_selection.SetReferencePoint( module->GetPosition() );
|
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
|
// pick the component up and start moving
|
||||||
m_toolMgr->RunAction( PCB_ACTIONS::move, true );
|
m_toolMgr->RunAction( PCB_ACTIONS::move, true );
|
||||||
|
|
||||||
// restore the previous cursor position
|
|
||||||
viewCtrls->SetCursorPosition( cursorPosition, false );
|
|
||||||
}
|
}
|
||||||
|
|
||||||
return 0;
|
return 0;
|
||||||
|
|
Loading…
Reference in New Issue