emanuelbuholzer / blender-urmoco Goto Github PK

When using the startup operator payloads should be checked. The operator should raise an error if the payload is negative and a warning if it is zero.

Movement triggers from within Dragonframe while we're not capturing queue up. Once you press "Start capturing" these queued up commands get executed, which can lead to unexpected movements. These queued up movements should get cleared before starting capturing.

The sync timer should start and stop whenever the scheduler powers on or off the backend.

Given that you've triggered a move in capturing mode and the robot is moving and you click "Stop capturing", the ghost robot stops moving, even though the robot is still moving. The robot should stop its movement gracefully and sync with the ghost until the robot comes to a full stop.