nAxesGenerator of motion_control stack bug


The nAxesGeneratorPos doesn't read the current position value when
moveTo(position, time) is called (opposed to the moveToDelayed).
Therefore, when calling a moveTo, the component thinks he is at an old
location value that was put there when the component was started.
Proposed patch in attachement.