Added a recording system - will be expanding this to record the inputs and convert them to the TimeLineItem objects to be put into the trainer
Added and renamed new buttons for recording
Reorganised files to allow morein depth access to TPInputLibrary
Merge branch 'master' of https://github.com/Necrophagos/SF4ComboTrainer into Recording_System

# By Necrophagos (2) and Michael Lee (1)
# Via Necrophagos
* 'master' of https://github.com/Necrophagos/SF4ComboTrainer:
  Bugfix with moveup-down fixed, more ibuki trials
  Minor performance tweak
  graphics on buttons and quick input options for editing moves attribution of images needs to be given to http://strategywiki.org/wiki/User:Blendmaster

Conflicts:
	SF4ComboTrainer/Form1.Designer.cs
	SF4ComboTrainer/Form1.cs
Finally have the inputs being recorded - processed and accepted async by the form whenever a frame passes by in game.
Next Step: Need to handle the system actually processing [Hold] and [Release] commands for inputs.
Merge remote-tracking branch 'GH_NecroPhage/master' into Recording_System
SF4Control and SF4Memory - refactored the variables and methods to meet CamelCase standards.

public variables and methods all start with Uppercase and follow with Uppercase on the start of each word.
private variables and methods all start with lowercase and follow with Uppercase on the start of each word.
Made a proper Deconstructor for the TimeLineItem roadie. Made it protected static and provided a Dispose method.
More work on getting methods and public variables to a good coding standard. Have renamed and rearranged code to read camelCase and ProperCase as well as bringing variables to the top of classes.
Huge changes to implement Model-View-ViewModel. Separation of the view and the project model will let us improve the view without drastically changing the implementation of the backed.
 It also means we can work on optimisation for the backend separately and use Unit Tests to ensure we're capturing/writing game data appropriately.
Creating the ViewModels for the TimeLine and the TimeLineItems.

The TimeLine ViewModel is essentially the entire business logic behind the form. It will interact with the SF4Record[<- SF4Control] and route all commands and events to the form through binding.
Merge branch 'Separated_View_and_Model' of https://github.com/thopiddock/SF4ComboTrainer into Recording_System
Renamed image files to be consistent in the View Project
Model contains TPLibrary - no need to have a separate project for Input
Some style clean up in the Main Form and removing the old references to ObserableObject and RelayCommand - the folder has been renamed to PropertyObjects from Interface Objects (it was too broad to call interfaces)
Merge remote-tracking branch 'origin/Recording_System' into Separated_View_and_Model
Creating the ViewModels for the TimeLine and the TimeLineItems.

The TimeLine ViewModel is essentially the entire business logic behind the form. It will interact with the SF4Record[<- SF4Control] and route all commands and events to the form through binding.
Renamed image files to be consistent in the View Project
Model contains TPLibrary - no need to have a separate project for Input
Some style clean up in the Main Form and removing the old references to ObserableObject and RelayCommand - the folder has been renamed to PropertyObjects from Interface Objects (it was too broad to call interfaces)