DataChannel objects are copied when they are prepped for acquisition. Also, the copy constructor for DataChannel did not inherit the recording, enabled, or monitored state from the original when it is copied.

Changing the state during acquisition resulted in changing the copy as desired, but not updating the original. Stopping acquisition and resuming would not be up to date with user configuration. Changing state before enabling acquisition would not propagate to the copy, because the copy constructor hardcoded the value. Both of these issues were changed in this commit.

Since RecordNodes are handled in the same way, it is likely that this bug exists there too. However that behavior has not been changed yet.

Fix bug when adding a Source input to LfpViewerAlpha with canvas open

Fix EventBroadcaster Windows linker include directories, which fixes …

Add X11 window size hint to juce library code for minimum window dimensions

(Audio playing is still not working properly, but at least it won't cause
crashes)

(Audio playing is still not working properly, but at least it won't cause
crashes)