[Feature Request] Movement Step Size Option

[agryson]

I often need to move my object around to ensure I crop to the smallest size.
Currently the step size is fixed and the latency between move, generate preview, UI becomes usable again adds frustrating delay.

My CNCs and 3D pritners give a "stepsize increment" so I can move by 1mm, 10mm or 100mm increments.

Obviously this is limited by endstops (physical or software) to prevent out of bounds.

This is already in the manual calibration to some degree where I can choose between 1° and 5° increments

It would be very helpful to have similar functionality during scan setup.

[esto-openscan]

I understand the issue, and in principle this should be possible to add. I'm just not sure yet what the best UX would be.

Would it be enough to have a configurable movement step size in the settings, which is then used for the movement controls? Or would you rather expect the fine-tuning / step size controls to be directly available on the scan setup page?

Since you're using this quite regularly, I'd be interested to know which approach would fit your workflow better.

[agryson]

The main thing would be to have 2 or more increments such as "fine" + "coarse" whether it's configurable or not.
If it's not configurable, you would just need sensible defaults and/or a wide enough range.

The specific numbers kind of depend on the case - so configurability would be great but if difficult to implement may be overkill.

Here are some examples from CNC softwares that show how the presets are used (often but not always with a numeric input for custom values), note that they fairly consistently let the user first choose a step size, then choose a movement direction - this is referred to as 'jog mode' if you want to search for other UIs:

(circled bottom right)

(top left)

(right hand side)

[esto-openscan]

I'm experimenting with this dropdown:

I'm not sure about representing the values as angles, though. For me, it's quite intuitive but maybe not for someone less familiar with the movement mechanics of the firmware.