the user may want to suspend the scanning and resume it

[Marzona]

Scanning happens by tuning different frequencies, using a step to define the next frequency to be tuned.
Sometimes you spot a possible signal exactly in the middle of two tuned frequencies.. aka your scanning granularity is high enough.

One way to solve the issue is to reduce the size of the scanning step, another handy option would be to suspend the scanning, tune manually the signal and them resume the scanning from where it has been suspended.

When the scanning gets resumed it should re-read the scanning configuration (except the upper limit of the frequency range) so to update the scanning "while it is going"