Now, when the user clicks on a tab in the DataViewport, the corresponding Editor becomes
active. Likewise, when the user selects an Editor with a Visualizer, the corresponding
tab becomes active in the DataViewport.

Since every processor now gets asked to enable() prior to the start of
acquisition, it's much simpler to move the steps involved in preparing
for acquisition into these methods. This the processor from beginning
acquisition when prepareToPlay() is called upon initialization.

When an LfpDisplayCanvas was hidden for more than a few seconds, it would lose
track of the displayBufferIndex, causing it to pause for a few seconds when
it comes back into view. Now, the DataViewport sends a "refresh" reminder
to the canvas, to remind it to update its buffer indices in order to
display new data.