Yes, my first version has implemented exactly this, but then I have realized that we don't have an atomic 
FetchAndStore for ControlValueAtomic which is required here. The code is now like that in a case of a race condition, an outdated seek is lost, and the current seek is executed twice. That is not too bad.