works ok with RHD data

Allows parameters to be set from saved XML and changes the
parameterEditor buttons (currently for discrete parameters only) to
reflect which parameters are currently used by selected and
non-selected channels. This fixes a problem where the buttons would
always show what the last press was rather than the current values for
the active channels (e.g. If you changed the parameters on Channel 2,
and then switched to select only Channel 1, the GUI would incorrectly
indicate that the settings for Channel 2 were active). Additionally,
allows the user to see what parameter values are used for channels not
currently selected.

- Clean up methods in GenericProcessor
- File selection now happens outside of EditorViewport
- Add mechanism for saving custom parameters for individual channels
- Settings file is automatically saved at the start of recording

Some caveats:
- If a source doesn't generate its own timestamps, all timestamps will be
  zero. This is obviously bad, so we need a way to protect this
  from happening.
- If there are multiple timestamps from different sources, they might
  conflict. Again, something needs to be done about this in the near future.
- If only a 32-bit timestamp is given, it needs to be shifted by 8 bits
  to fit in our 64-bit timestamp slot

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.

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!

When many channels are selected for recording a race condition can cause a crash by writing to a file that has not been opened yet.

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>

Weird behavior was observed during fwrite when files were only opened
with "a". fwrite did not write the expected number of bytes (probably
augumented things with a \n or \r). This caused serious problems parsing
the dumped files in matlab. Forcing a binary fopen option fixed things.