[Elecraft] Intuiting the K2 tuning rate

[Robert Block]

Somehow, I always find myself using the wrong tuning rate on my K2.

When and if the MCU is upgraded with additional code space, I'd like to 
see an autorate for tuning.

By noting the elapsed time between pulses from the encoder, the software 
can note how fast the dial is being spun.  Fast implies that user wants to 
do a big QSY or rapidly scan the band.  Slow implies the user is carefully 
zeroing in on the target.  Combined with the selected mode, it should be 
possible to make the tuning be smooth and intuitive.