antonpup / Aurora

… updated twice in a single frame when the Aurora window was not focused or the "Show Overlays in Application Preview" is checked.

…es the state if that boolean is true.

Renamed `Boolean_Latch` to `Boolean_FlipFlopSR`.

How dumb am I to not notice this bug at first... :(

Could've fixed the binding but decided to remove it, otherwise in many places there would be repeated labels.

This allows re-creating the MMDevice on the correct thread. The device is only recreated if the ID has changed, so the only overheard of calling it each frame is a string comparison.

…or the local pc inf game state.

Changing the gamestate device requires a restart.

…ices on-the-fly.

Helps with easily swapping devices on-the-fly.

…debug

…tion-rewrite-2

…es of certain types (GameStates, Nodes and IEnumerable<Node>s).

…ome redundant code in 5aa7a35.

This is because the value may not actually be the current value if the evaluatable isn't updated (e.g. in a false branch of an if-else).

…erride in the editor UI.

Now 'Evaluate' is handled by the abstract Evaluatable{T}, which calls a protected abstract 'Execute' method. This 'Execute' is that one that should be overriden to provide evaluatable logic. 'Evaluate' should still be called when getting the value from an evaluatable.
The most recent value from evaluatables is now stored, with the aim of helping to provide debugging information.

Removed the IGameState constructor from game states.

… 'AnythingChanged' event.

Added FastMember as a replacement.