To run this in the future, install astyle (sudo apt-get install astyle),
then enter the following from the top-level project directory:

astyle --options=astyle.options --recursive "./Source/*.cpp" "./Source/*.h"

This will convert tabs to 4 spaces and ensure that brackets are on
their own lines.

Using ScopedPointers was causing memory leaks. It's worth tracking
down the source of these in the future, but for now, we'll leave
the code as it was before.

Use the following command to update the copyright year in all files,
starting in the Source/ directory:

find . -type f -print0 | xargs -0
   sed -i 's/Copyright (C) 2012/Copyright (C) 2013/g'

Works like a charm!

The main UI components now use ScopedPointers for their children,
alleviating the need to call "deleteAllChildren" or "deleteAndZero"
in the destructor.

Generic changes:

- Genuinely unused variables (-Wunused-variable): delete
  them. Sometimes add a comment if the variable is for an extension of
  the code that isn't done yet.

- Variables that became unused due to commented-out
  code (-Wunused-variable): comment out their definitions. Dirty, but
  that's because commenting out code instead of deleting it is
  dirty.

  Many of these are due to commented-out printlines that should have
  been log messages that only get emitted at high verbosity level.

Specific changes:

- SpikeObject.cpp (-Wunused-value): move initialization of loop
  variable into first for loop clause to silence the warning.

Signed-off-by: Marti Bolivar <mbolivar@leaflabs.com>

Rearrange member initialization in constructors to silence GCC
-Wreorder warnings (-Wreorder is enabled by -Wall).

Signed-off-by: Marti Bolivar <mbolivar@leaflabs.com>

Uses the parameters array to create XML data for parameter settings on
each channel when saving.

This only works for processors that use the parameters array, though I
updated LFP and Signal Generator to update that in parallel (LFP seems
to have an unrelated bug in dealing with channels that is causing some
problems). Eventually, all parameters should be used in the parameters
array, since it opens up a lot of possible holes when using default
values (they need to be specified twice), and once loading is
implemented. I've fixed some of the problems with parameters, so this
should be easier to do.

As part of this, I also fixed the implementation of
addParameterEditors. The old way of implementing a custom parameter
editor was to rewrite the virtual function, but because it was called
in the constructor, this didn't work (constructors use the type of the
parent). Instead, all editors now also pass a bool
"useDefaultParameterEditors" which is used by addParameterEditors() to
determine whether to do anything. I think this is the best way to do
it. It's initialized to default as true, though I had some trouble with
it implicitly taking the argument and so had to add true to most of the
editor functions (which is probably good practice anyway).

I also fixed some of the functions for generic processor to get
parameter index and parameter name.

Obviously, this is of considerable less use without functions for
loading parameters, but I figured it'd be better to make available for
testing with just the loading in case the changes to Parameters broke
anything I missed.

Before, EditorViewport would start accessing arrays on keypresses (specifically
the arrow keys) even when there were no editors.  This adds an extra check to
prevent this.

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.

Channel selection now takes place within a slick new interface. It's not
yet tied to actually changing parameters, but things should be much simpler
code-wise, as well as visually.

The AudioComponent now closes the audio device when it's not in use,
saving CPU cycles. Previously, background CPU levels would be between
8 and 10%. Now, when acquisition is not active (and audio device settings
are not being actively edited), background CPU levels drop to 2%. More
optimization will be necessary to get it down to zero, but 2% is still
a big improvement over what we had previously.

Major modifications to EditorViewport::loadState() and
EditorViewport::saveState() allow complex signal chains to be loaded
and saved. There are still some issues with editor button status
on startup, but these should be easy to fix.

The EditorViewport now contains buttons to scroll through multiple tabs,
or scroll across long signal chains. Now, there can be infinitely
many signal chains of infinite length (if you have a lot of time
on your hands).

Functions for managing the signal chain are no longer handled by
the EditorViewport, but by the SignalChainManager