Comment 4 for bug 1547916

Revision history for this message
Uwe Klotz (uklotzde-deactivatedaccount) wrote : Re: interface freeze on "reset tempo and beatgrid"

We don't need a separate worker thread. I already have an idea in my mind how such a reactive, event-loop-driven TrackActionScheduler can be implemented efficiently:
- shared queue of pending track ids
- queue of pending actions: action functor working on a single TrackPointer, number of total tracks, number of finished tracks

Some parts of the new TrackAnalysisScheduler might be reusable.