* Rewind & State config - remove the default option
* remove the savestate type of default, not that this is a breaking config change for anyone that had specifically set savestates to text
* remove BinaryStatesPreferred from IStatable and use config setting when starting movies from "Now" in record movie dialog
* remove BinaryStatesPreferred from cores
* make text savestates an extension method off of IStatable and an inteface ITextStatable it uses if the core implements it. This will allow cores to opt in to text states if desired
* make cores with actual text savestate impleemntations get ITextStatable, remove text state logic from cores that just have a binary as as text implementation
* virtu - tabs instead of spaces
* virtu - use nooget for Newtonsoft.Json
* virtu - target .net 4.8
* resharper - target C# 8
* virtu - remove unused usings
* virtu - remove some unused code
* virtu - cleanups
* virtu - trace logging - add flags to trace logs
* virtu - cleanups
* virtu - misc cleanups
* virtu - make some stuff internal and simplify the api some
* virtu - clock down more things and simplify api more
* virtu - lock api down more
* virtu- simplify, breaks older savestates however
* virtu - simplify more
* virtu - cleanup
* virtu- more cleanup
* virtu - reorg some files
* virtu - more cleanup
* virtu - more reorg
* virtu - more reorg
* virtu - make more things internal instead of public
* virtu - make more things internal
* virtu - update dll
* cleanup
* virtu - reorg
* virtu - remove unitialize from machine component since nothing was utilizing it
* virtu - simplify api
* virtu - cleanup
* virtu - cleanup and lock things down
* virtu - lock down and cleanup
* virtu - cleanup
* virtu - simplify - breaks savestates
* virtu - make PeripheralCard an interface with default implementation, breaks savestates
* virtu - minimize use of machine component
* virtu - cleanup
* virtu - start minimizing dependencies
* virtu - cleanup
* virtu - simplify
* apple II - simplify
* virtu - move some biz logic into bizhawk
* virtu - git rid of MachineComponent
* virtu - delete no longer needed code
* virtu - reorg
* move serialization logic out of virtu and into bizhawk, this was our shenanigans
* virtu - some small cleanups
* virtu - simplify
* virtu - dependency minimization
* virtu - minimize dependencies
* minimize dependencies
* virtu - move drivelight property into component that controls it
* virtu - minimize dependencies
* virtu - minimize depenencies
* move some machine logic to memory class
* move some initialize logic into constructor
* move initialize logic to constructor
* move logic from Initialize to constructor
* move initialize logic to constructor, simplify api to bizhawk
* dll
* virtu - movie some logic back into bizhawk
* virtu - move Lagged property from machine to memory component
* move more biz logic from virtu to biz
* virtu - slight reorg
* virtu - move some reset logic to constructor
* virtu - move some stuff around
* virtu - declare dependencies in memory class, no more dependencies on the machine class
* move slots from machine to memory class
* move some properties from machine to memory
* move more things into the memory class
* remove Machine.cs from virtu and make an equivalent container in bizhawk
* virtu - cleanup
* interface the cassette class and create a biz empty cassette "implementation"
* move some more dummy logic from virtu to biz and put an interface in virtu
* virtu - use an interface for a dependency
* virtu - interface more things
* virtu - more interfacing of things
* virtu - interface more things
* apple II/virtu - some reorg
* virtu - cleanup
* virtu - remove unused usages of disk name in disk classes
* virtu- cleanup and simplify api
* virtu - remove unused BootDrive property
* virtu - cleanup and interface more
* cleanup
* update virtu dll
also BEWARE: note the change to UpdateInput(). This was a brain-dead mistake as far as I can tell (just look at it, it seems obvious), and it came from a commit where I said "I tested it for 20 seconds" so it was probably rushed. However, fixing this to something sensible MAY affect sync. If it's important, we could roll it back. However I think UpdateInput is more like a "latch user input" than a "tick internal counters" so it may be safe
TiKevin83