UI problem with milliseconds scan speed setting

[Mats Lundälv]

UI experiences from other OSK settings clearly indicate that many users have problems with handling a milliseconds resolution in the settings.
Ideally aim at a slider/wheel scale increasing/decreasing speed by a proportional percentage factor of 5-10% - presenting the speed in seconds with a 2 decimals resolution (in a range of e.g. 0.20 - 3.00 sec)

[Mats Lundälv (mats-lundalv)]

Further justification:

The problem with a few steps in the speed settings is that, though this is very user friendly in the settings procedure, it is very user unfriendly for the acual use of the software. Especially so for users who can cope with, and need, faster scanning speeds, as the speed setting steps become absurdley coarse when you are in the faster speed ranges, right?

So presenting enough fine-grained fixed steps also for the fast scan speed users means that you have to provide a rather long list of alternative scan speeds - which again makes it less user-friendly in the settings procedure. Then again the slider/wheel option becomes interesting, especially if it takes care of the settings in a smart way by providing a proportional scale rather than a linear scale. But of course you could provide this also in a straight list of alternative speeds.
 /ML

[Jorge Silva (jorge-silva)]

A draft implementation with a slider has been committed. This implementation is linear in the conversion from speed to delay. A different non-linear implementation may be needed to avoid low resolution in the higher speed values.

[Jorge Silva (jorge-silva)]

A new implementation involving consecutive 20% increments of speed has been committed. This works well in terms of usability so it'll be the one used.