mess; developing the engine in sub-branches

There's very little useful information about awaiting events from a
C++/CX code (or any language for that matter), so I'll pick up the
approach with events causing state changes in another branch and wait
for more info to pop up with this one.
compilable code; board change; back to master;

Solution compiles for the first time. Board changed from a bunch of
buttons, each having its own handler, to a single canvas; still need to
solve the issue with drawing images on it. Back to master; the idea with
having events handling local changes and threads handling networking
seems to be the right one to take here. Might need to backtrack once I
get to implementing networking. Next TODO: more interface work.