Removed the element tree out of the Configure Elements form and made it a generic control. Hopefully should have same functionality as before at this stage.
Add the ability to disable dragging in the element treeview.
- Updates & Changes to the sequencer rendering
- New queueing engine for background rendering of sequencer effects
- Changes to the way zoom and unzoom renders in the sequencer
Revert "Error Handling in parallel operations"

This reverts commit ddb35b996538482f7e8284ae76edecce654e164f.
Changed controller list to sort ascending
- Change the ICommand and ICombinator interfaces to not have a result-type templated interface. It added extra complexity, and made a 'generic' command returning class difficult.
Added a 'Discard Excess' combinator -- throws away all but a single command.
Added a Debug Output controller: shows the command types and values for the incoming commands.
Fix up scale issues with 16, 32 and 64 bit values.
Simplify Evaluators to not try and handle CommandValue intents themselves: that's not the point of CommandValue intents; the point of them is to wrap and pass a specific command through to the controller.  If the controller doesn't know what to do with it, well.... tough.
Add a 'StringCommand' class.
Ooops.... let's not cause many null reference exceptions when people try and combine command values. My bad.
Add a 'Static Intent' type, to complement the Linear Intent type. Use it for the CommandValue Intent instead.
Add new CustomValue effect type and editor -- essentially, wraps a CommandValueIntent to be able to pass integral values, strings, etc. directly to the controller.
Add support for the 'string' command in the debug output controller.
Update the CustomValue effect editor dialog properly on first open (disabling controls).
Use the right bloody element GUID when generating data! arrrrrrgh....
Add an extra version label that shows the build number on the main form if non-zero.
Add a bit of sanity around the thread starting in UIThread when kicking off extra forms and message queues.
Add a bit of error checking for ModuleData objects in the Display Preview.  It's not a proper fix -- just patching symptoms -- as the root cause is in the framework module instantiation and data object creation/assignment. Yay threads!