format

Author: bmalrat

Assets/Tests/InputSystem/Plugins/OnScreenTests.cs

@@ -372,15 +372,15 @@ public void Devices_DisablingLastOnScreenControlDoesReportActiveControl()
         var gameObject = new GameObject();
 
         Assert.That(OnScreenControl.HasAnyActive, Is.False);
-        
+
         var buttonA = gameObject.AddComponent<OnScreenButton>();
 
         Assert.That(OnScreenControl.HasAnyActive, Is.True);
 
         var buttonB = gameObject.AddComponent<OnScreenButton>();
         buttonA.controlPath = "/<Keyboard>/a";
         buttonB.controlPath = "/<Keyboard>/b";
-        
+
         Assert.That(OnScreenControl.HasAnyActive, Is.True);
 
         buttonA.enabled = false;

Assets/Tests/InputSystem/Plugins/PlayerInputTests.cs

@@ -670,7 +670,7 @@ public void PlayerInput_AutoSwitchControlSchemesInSinglePlayerWithOnScreenContro
     {
         var keyboard = InputSystem.AddDevice<Keyboard>();
         var mouse = InputSystem.AddDevice<Mouse>();
-       
+
         var go = new GameObject();
 
         var onScreenButton = go.AddComponent<OnScreenButton>();

Packages/com.unity.inputsystem/InputSystem/Plugins/OnScreen/OnScreenControl.cs

@@ -35,13 +35,13 @@ namespace UnityEngine.InputSystem.OnScreen
     /// types of device layouts (e.g. one control references 'buttonWest' on
     /// a gamepad and another references 'leftButton' on a mouse), then a device
     /// is created for each type referenced by the setup.
-    /// 
+    ///
     /// The <see cref="OnScreenControl"/> works by simulating events from the device specified in the <see cref="OnScreenControl.controlPath"/>
     /// property. Some parts of the Input System, such as the <see cref="PlayerInput"/> component, can be set up to
     /// auto-switch <see cref="PlayerInput.neverAutoSwitchControlSchemes"/> to a new device when input from them is detected.
     /// When a device is switched, any currently running inputs from the previously active device are cancelled.
     ///
-    /// To avoid this situation, you need to ensure, depending on your case, that the Mouse, Pen, Touchsceen and/or XRController devices are not used in a concurent 
+    /// To avoid this situation, you need to ensure, depending on your case, that the Mouse, Pen, Touchsceen and/or XRController devices are not used in a concurent
     /// control schemes of the simulated device.
     /// </remarks>
     public abstract class OnScreenControl : MonoBehaviour
@@ -217,8 +217,7 @@ protected void SentDefaultValueToControl()
             InputSystem.QueueEvent(m_InputEventPtr);
         }
 
-
-        // Used by PlayerInput auto switch for scheme to prevent using Pointer device. 
+        // Used by PlayerInput auto switch for scheme to prevent using Pointer device.
         internal static bool HasAnyActive => s_nbActiveInstances != 0;
         private static int s_nbActiveInstances = 0;
 

Packages/com.unity.inputsystem/InputSystem/Plugins/OnScreen/OnScreenStick.cs

@@ -25,12 +25,12 @@ namespace UnityEngine.InputSystem.OnScreen
     /// property. Some parts of the Input System, such as the <see cref="PlayerInput"/> component, can be set up to
     /// auto-switch <see cref="PlayerInput.neverAutoSwitchControlSchemes"/> to a new device when input from them is detected.
     /// When a device is switched, any currently running inputs from the previously active device are cancelled.
-    /// In the case of <see cref="OnScreenStick"/>, this can mean that the <see cref="IPointerUpHandler.OnPointerUp"/> method will be called 
+    /// In the case of <see cref="OnScreenStick"/>, this can mean that the <see cref="IPointerUpHandler.OnPointerUp"/> method will be called
     /// and the stick will jump back to center, even though the pointer input has not physically been released.
     ///
     /// To avoid this situation, set the <see cref="useIsolatedInputActions"/> property to true. This will create a set of local
     /// Input Actions to drive the stick that are not cancelled when device switching occurs.
-    /// You might also need to ensure, depending on your case, that the Mouse, Pen, Touchsceen and/or XRController devices are not used in a concurent 
+    /// You might also need to ensure, depending on your case, that the Mouse, Pen, Touchsceen and/or XRController devices are not used in a concurent
     /// control schemes of the simulated device.
     /// </remarks>
     [AddComponentMenu("Input/On-Screen Stick")]