Step input popover is a bit cumbersome to use

[axelboc]

The step input popover has a few flaws:

• It requires too many user interactions to change the step.
• The up/down arrow buttons to adjust the step are apparently rarely used because it's often quicker to enter a value manually (especially since some of the increments are not well configured by default - e.g. 0.1 for Omega is way too small).
• The checkmark button feels unnecessary since one is already typing a value, so pressing Enter is faster.
• When the step changes, the motor input becomes "dirty" for no apparent reason (i.e. orange background, indicating that the value of the input has changed but hasn't yet been sent to the server).

Proposal: Turn the step value into an input field that can be edited directly and committed with Enter (no up/down arrow buttons). The step input should be marked as dirty when edited but not yet committed (but not the motor input).

This solution would also greatly simplify the logic of the step component, since it currently deals with disabling the popover behaviour when the motor input is already displayed inside a popover:

[marcus-oscarsson]

Yes, the step function is indeed not used very often. Your suggestions sounds good to me as well, lets go for that if there are no other objections :)