Merge pull request #132 from AliRezaBeigy/master

fix: mouse movement issue -> Thanks a lot to @AliRezaBeigy

Author: Gh0stWalk3r

src/GregsStack.InputSimulatorStandard/InputBuilder.cs

@@ -274,8 +274,8 @@ public InputBuilder AddAbsoluteMouseMovement(int absoluteX, int absoluteY)
         {
             var movement = new Input { Type = (uint)InputType.Mouse };
             movement.Data.Mouse.Flags = (uint)(MouseFlag.Move | MouseFlag.Absolute);
-            movement.Data.Mouse.X = absoluteX;
-            movement.Data.Mouse.Y = absoluteY;
+            movement.Data.Mouse.X = (int)((absoluteX * 65536) / NativeMethods.GetSystemMetrics((uint)SystemMetric.SM_CXSCREEN));
+            movement.Data.Mouse.Y = (int)((absoluteY * 65536) / NativeMethods.GetSystemMetrics((uint)SystemMetric.SM_CYSCREEN));
 
             this.inputList.Add(movement);
 

src/GregsStack.InputSimulatorStandard/Native/NativeMethods.cs

@@ -13,35 +13,35 @@ internal static class NativeMethods
         /// </summary>
         /// <param name="virtualKeyCode">Specifies one of 256 possible virtual-key codes. For more information, see Virtual Key Codes. Windows NT/2000/XP: You can use left- and right-distinguishing constants to specify certain keys. See the Remarks section for further information.</param>
         /// <returns>
-        /// If the function succeeds, the return value specifies whether the key was pressed since the last call to GetAsyncKeyState, and whether the key is currently up or down. If the most significant bit is set, the key is down, and if the least significant bit is set, the key was pressed after the previous call to GetAsyncKeyState. However, you should not rely on this last behavior; for more information, see the Remarks. 
-        /// 
-        /// Windows NT/2000/XP: The return value is zero for the following cases: 
+        /// If the function succeeds, the return value specifies whether the key was pressed since the last call to GetAsyncKeyState, and whether the key is currently up or down. If the most significant bit is set, the key is down, and if the least significant bit is set, the key was pressed after the previous call to GetAsyncKeyState. However, you should not rely on this last behavior; for more information, see the Remarks.
+        ///
+        /// Windows NT/2000/XP: The return value is zero for the following cases:
         /// - The current desktop is not the active desktop
         /// - The foreground thread belongs to another process and the desktop does not allow the hook or the journal record.
-        /// 
+        ///
         /// Windows 95/98/Me: The return value is the global asynchronous key state for each virtual key. The system does not check which thread has the keyboard focus.
-        /// 
-        /// Windows 95/98/Me: Windows 95 does not support the left- and right-distinguishing constants. If you call GetAsyncKeyState with these constants, the return value is zero. 
+        ///
+        /// Windows 95/98/Me: Windows 95 does not support the left- and right-distinguishing constants. If you call GetAsyncKeyState with these constants, the return value is zero.
         /// </returns>
         /// <remarks>
-        /// The GetAsyncKeyState function works with mouse buttons. However, it checks on the state of the physical mouse buttons, not on the logical mouse buttons that the physical buttons are mapped to. For example, the call GetAsyncKeyState(VK_LBUTTON) always returns the state of the left physical mouse button, regardless of whether it is mapped to the left or right logical mouse button. You can determine the system's current mapping of physical mouse buttons to logical mouse buttons by calling 
+        /// The GetAsyncKeyState function works with mouse buttons. However, it checks on the state of the physical mouse buttons, not on the logical mouse buttons that the physical buttons are mapped to. For example, the call GetAsyncKeyState(VK_LBUTTON) always returns the state of the left physical mouse button, regardless of whether it is mapped to the left or right logical mouse button. You can determine the system's current mapping of physical mouse buttons to logical mouse buttons by calling
         /// Copy CodeGetSystemMetrics(SM_SWAPBUTTON) which returns TRUE if the mouse buttons have been swapped.
-        /// 
+        ///
         /// Although the least significant bit of the return value indicates whether the key has been pressed since the last query, due to the pre-emptive multitasking nature of Windows, another application can call <see cref="GetAsyncKeyState"/> and receive the "recently pressed" bit instead of your application. The behavior of the least significant bit of the return value is retained strictly for compatibility with 16-bit Windows applications (which are non-preemptive) and should not be relied upon.
-        /// 
-        /// You can use the virtual-key code constants VK_SHIFT, VK_CONTROL, and VK_MENU as values for the vKey parameter. This gives the state of the SHIFT, CTRL, or ALT keys without distinguishing between left and right. 
-        /// 
-        /// Windows NT/2000/XP: You can use the following virtual-key code constants as values for vKey to distinguish between the left and right instances of those keys. 
-        /// 
-        /// Code Meaning 
-        /// VK_LSHIFT Left-shift key. 
-        /// VK_RSHIFT Right-shift key. 
-        /// VK_LCONTROL Left-control key. 
-        /// VK_RCONTROL Right-control key. 
-        /// VK_LMENU Left-menu key. 
-        /// VK_RMENU Right-menu key. 
-        /// 
-        /// These left- and right-distinguishing constants are only available when you call the GetKeyboardState, SetKeyboardState, GetAsyncKeyState, GetKeyState, and MapVirtualKey functions. 
+        ///
+        /// You can use the virtual-key code constants VK_SHIFT, VK_CONTROL, and VK_MENU as values for the vKey parameter. This gives the state of the SHIFT, CTRL, or ALT keys without distinguishing between left and right.
+        ///
+        /// Windows NT/2000/XP: You can use the following virtual-key code constants as values for vKey to distinguish between the left and right instances of those keys.
+        ///
+        /// Code Meaning
+        /// VK_LSHIFT Left-shift key.
+        /// VK_RSHIFT Right-shift key.
+        /// VK_LCONTROL Left-control key.
+        /// VK_RCONTROL Right-control key.
+        /// VK_LMENU Left-menu key.
+        /// VK_RMENU Right-menu key.
+        ///
+        /// These left- and right-distinguishing constants are only available when you call the GetKeyboardState, SetKeyboardState, GetAsyncKeyState, GetKeyState, and MapVirtualKey functions.
         /// </remarks>
         [DllImport("user32.dll", SetLastError = true)]
         public static extern short GetAsyncKeyState(ushort virtualKeyCode);
@@ -50,27 +50,27 @@ internal static class NativeMethods
         /// The <see cref="GetKeyState"/> function retrieves the status of the specified virtual key. The status specifies whether the key is up, down, or toggled (on, off alternating each time the key is pressed). (See: http://msdn.microsoft.com/en-us/library/ms646301(VS.85).aspx)
         /// </summary>
         /// <param name="virtualKeyCode">
-        /// Specifies a virtual key. If the desired virtual key is a letter or digit (A through Z, a through z, or 0 through 9), nVirtKey must be set to the ASCII value of that character. For other keys, it must be a virtual-key code. 
+        /// Specifies a virtual key. If the desired virtual key is a letter or digit (A through Z, a through z, or 0 through 9), nVirtKey must be set to the ASCII value of that character. For other keys, it must be a virtual-key code.
         /// If a non-English keyboard layout is used, virtual keys with values in the range ASCII A through Z and 0 through 9 are used to specify most of the character keys. For example, for the German keyboard layout, the virtual key of value ASCII O (0x4F) refers to the "o" key, whereas VK_OEM_1 refers to the "o with umlaut" key.
         /// </param>
         /// <returns>
-        /// The return value specifies the status of the specified virtual key, as follows: 
+        /// The return value specifies the status of the specified virtual key, as follows:
         /// If the high-order bit is 1, the key is down; otherwise, it is up.
         /// If the low-order bit is 1, the key is toggled. A key, such as the CAPS LOCK key, is toggled if it is turned on. The key is off and untoggled if the low-order bit is 0. A toggle key's indicator light (if any) on the keyboard will be on when the key is toggled, and off when the key is untoggled.
         /// </returns>
         /// <remarks>
-        /// The key status returned from this function changes as a thread reads key messages from its message queue. The status does not reflect the interrupt-level state associated with the hardware. Use the GetAsyncKeyState function to retrieve that information. 
-        /// An application calls GetKeyState in response to a keyboard-input message. This function retrieves the state of the key when the input message was generated. 
-        /// To retrieve state information for all the virtual keys, use the GetKeyboardState function. 
-        /// An application can use the virtual-key code constants VK_SHIFT, VK_CONTROL, and VK_MENU as values for the nVirtKey parameter. This gives the status of the SHIFT, CTRL, or ALT keys without distinguishing between left and right. An application can also use the following virtual-key code constants as values for nVirtKey to distinguish between the left and right instances of those keys. 
+        /// The key status returned from this function changes as a thread reads key messages from its message queue. The status does not reflect the interrupt-level state associated with the hardware. Use the GetAsyncKeyState function to retrieve that information.
+        /// An application calls GetKeyState in response to a keyboard-input message. This function retrieves the state of the key when the input message was generated.
+        /// To retrieve state information for all the virtual keys, use the GetKeyboardState function.
+        /// An application can use the virtual-key code constants VK_SHIFT, VK_CONTROL, and VK_MENU as values for the nVirtKey parameter. This gives the status of the SHIFT, CTRL, or ALT keys without distinguishing between left and right. An application can also use the following virtual-key code constants as values for nVirtKey to distinguish between the left and right instances of those keys.
         /// VK_LSHIFT
         /// VK_RSHIFT
         /// VK_LCONTROL
         /// VK_RCONTROL
         /// VK_LMENU
         /// VK_RMENU
-        /// 
-        /// These left- and right-distinguishing constants are available to an application only through the GetKeyboardState, SetKeyboardState, GetAsyncKeyState, GetKeyState, and MapVirtualKey functions. 
+        ///
+        /// These left- and right-distinguishing constants are available to an application only through the GetKeyboardState, SetKeyboardState, GetAsyncKeyState, GetKeyState, and MapVirtualKey functions.
         /// </remarks>
         [DllImport("user32.dll", SetLastError = true)]
         public static extern short GetKeyState(ushort virtualKeyCode);
@@ -91,7 +91,7 @@ internal static class NativeMethods
         public static extern uint SendInput(uint numberOfInputs, Input[] inputs, int sizeOfInputStructure);
 
         /// <summary>
-        /// The <see cref="GetMessageExtraInfo"/> function retrieves the extra message information for the current thread. Extra message information is an application- or driver-defined value associated with the current thread's message queue. 
+        /// The <see cref="GetMessageExtraInfo"/> function retrieves the extra message information for the current thread. Extra message information is an application- or driver-defined value associated with the current thread's message queue.
         /// </summary>
         /// <returns></returns>
         /// <remarks>To set a thread's extra message information, use the SetMessageExtraInfo function. </remarks>
@@ -114,5 +114,8 @@ internal static class NativeMethods
         /// <returns>Returns <c>true</c> if successful or <c>false</c> otherwise.</returns>
         [DllImport("user32.dll", SetLastError = true)]
         public static extern bool GetCursorPos(out Point lpPoint);
+
+        [DllImport("user32.dll")]
+        public static extern uint GetSystemMetrics(uint smIndex);
     }
 }

src/GregsStack.InputSimulatorStandard/Native/SystemMetric.cs

@@ -0,0 +1,102 @@
+namespace GregsStack.InputSimulatorStandard.Native
+{
+    /// <summary>
+    /// Specifies the type of the system metric. This member can be one of the following values.
+    /// </summary>
+    internal enum SystemMetric : uint
+    {
+            SM_CXSCREEN = 0,
+            SM_CYSCREEN = 1,
+            SM_CXVSCROLL = 2,
+            SM_CYHSCROLL = 3,
+            SM_CYCAPTION = 4,
+            SM_CXBORDER = 5,
+            SM_CYBORDER = 6,
+            SM_CXDLGFRAME = 7,
+            //SM_CXFIXEDFRAME = 7,
+            SM_CYDLGFRAME = 8,
+            //SM_CYFIXEDFRAME = 8,
+            SM_CYVTHUMB = 9,
+            SM_CXHTHUMB = 10,
+            SM_CXICON = 11,
+            SM_CYICON = 12,
+            SM_CXCURSOR = 13,
+            SM_CYCURSOR = 14,
+            SM_CYMENU = 15,
+            SM_CXFULLSCREEN = 16,
+            SM_CYFULLSCREEN = 17,
+            SM_CYKANJIWINDOW = 18,
+            SM_MOUSEPRESENT = 19,
+            SM_CYVSCROLL = 20,
+            SM_CXHSCROLL = 21,
+            SM_DEBUG = 22,
+            SM_SWAPBUTTON = 23,
+            SM_CXMIN = 28,
+            SM_CYMIN = 29,
+            SM_CXSIZE = 30,
+            SM_CYSIZE = 31,
+            //SM_CXSIZEFRAME = 32,
+            SM_CXFRAME = 32,
+            //SM_CYSIZEFRAME = 33,
+            SM_CYFRAME = 33,
+            SM_CXMINTRACK = 34,
+            SM_CYMINTRACK = 35,
+            SM_CXDOUBLECLK = 36,
+            SM_CYDOUBLECLK = 37,
+            SM_CXICONSPACING = 38,
+            SM_CYICONSPACING = 39,
+            SM_MENUDROPALIGNMENT = 40,
+            SM_PENWINDOWS = 41,
+            SM_DBCSENABLED = 42,
+            SM_CMOUSEBUTTONS = 43,
+            SM_SECURE = 44,
+            SM_CXEDGE = 45,
+            SM_CYEDGE = 46,
+            SM_CXMINSPACING = 47,
+            SM_CYMINSPACING = 48,
+            SM_CXSMICON = 49,
+            SM_CYSMICON = 50,
+            SM_CYSMCAPTION = 51,
+            SM_CXSMSIZE = 52,
+            SM_CYSMSIZE = 53,
+            SM_CXMENUSIZE = 54,
+            SM_CYMENUSIZE = 55,
+            SM_ARRANGE = 56,
+            SM_CXMINIMIZED = 57,
+            SM_CYMINIMIZED = 58,
+            SM_CXMAXTRACK = 59,
+            SM_CYMAXTRACK = 60,
+            SM_CXMAXIMIZED = 61,
+            SM_CYMAXIMIZED = 62,
+            SM_NETWORK = 63,
+            SM_CLEANBOOT = 67,
+            SM_CXDRAG = 68,
+            SM_CYDRAG = 69,
+            SM_SHOWSOUNDS = 70,
+            SM_CXMENUCHECK = 71,
+            SM_CYMENUCHECK = 72,
+            SM_SLOWMACHINE = 73,
+            SM_MIDEASTENABLED = 74,
+            SM_MOUSEWHEELPRESENT = 75,
+            SM_XVIRTUALSCREEN = 76,
+            SM_YVIRTUALSCREEN = 77,
+            SM_CXVIRTUALSCREEN = 78,
+            SM_CYVIRTUALSCREEN = 79,
+            SM_CMONITORS = 80,
+            SM_SAMEDISPLAYFORMAT = 81,
+            SM_IMMENABLED = 82,
+            SM_CXFOCUSBORDER = 83,
+            SM_CYFOCUSBORDER = 84,
+            SM_TABLETPC = 86,
+            SM_MEDIACENTER = 87,
+            SM_STARTER = 88,
+            SM_SERVERR2 = 89,
+            SM_MOUSEHORIZONTALWHEELPRESENT = 91,
+            SM_CXPADDEDBORDER = 92,
+            SM_DIGITIZER = 94,
+            SM_MAXIMUMTOUCHES = 95,
+            SM_REMOTESESSION = 0x1000,
+            SM_SHUTTINGDOWN = 0x2000,
+            SM_REMOTECONTROL = 0x2001
+    }
+}