Correcting the client's use of SynchronizationContext

If no SynchronizationContext is initialised, the client creates a new one for its internal use, otherwise it inherrits the existing one.

Fixes #328

Author: blackspherefollower

Buttplug.Client.Test/ButtPlugClientTests.cs

@@ -41,7 +41,6 @@ public ButtplugServer GetServer()
         [OneTimeSetUp]
         public void OneTimeSetUp()
         {
-            SynchronizationContext.SetSynchronizationContext(new SynchronizationContext());
             _logMgr = new ButtplugLogManager();
             _devMgr = new DeviceManager(new ButtplugLogManager());
             _subtypeMgr = new TestDeviceSubtypeManager();

Buttplug.Client/ButtplugWSClient.cs

@@ -1,13 +1,11 @@
 using System;
 using System.Collections.Concurrent;
 using System.Collections.Generic;
-using System.Text;
 using System.Threading;
 using System.Threading.Tasks;
 using Buttplug.Core;
 using Buttplug.Core.Messages;
 using JetBrains.Annotations;
-using SuperSocket.ClientEngine;
 using WebSocket4Net;
 using static Buttplug.Client.DeviceEventArgs;
 
@@ -97,7 +95,7 @@ public ButtplugWSClient(string aClientName)
             _bpLogger = _bpLogManager.GetLogger(GetType());
             _parser = new ButtplugJsonMessageParser(_bpLogManager);
             _bpLogger.Info("Finished setting up ButtplugClient");
-            _owningDispatcher = SynchronizationContext.Current;
+            _owningDispatcher = SynchronizationContext.Current ?? new SynchronizationContext();
             _tokenSource = new CancellationTokenSource();
         }