public override void Press()
{
if (IsInEffect)
{
InputSimulator.SimulateKeyUp(KeyCode);
}
else
{
InputSimulator.SimulateKeyDown(KeyCode);
}
// We need to use IsKeyDownAsync here so we will know exactly what state the key will be in
// once the active windows read the input from the MessagePump. IsKeyDown will only report
// the correct value after the input has been read from the MessagePump and will not be correct
// by the time we set IsInEffect.
IsInEffect = InputSimulator.IsKeyDownAsync(KeyCode);
OnKeyPressed();
}
/// <summary>
/// Determines whether a key is up or down at the time the function is called by calling the GetAsyncKeyState function. (See: http://msdn.microsoft.com/en-us/library/ms646293(VS.85).aspx)
/// </summary>
/// <param name="keyCode">The key code.</param>
/// <returns>
/// <c>true</c> if the key is down; otherwise, <c>false</c>.
/// </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
/// 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 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.
/// </remarks>
public bool IsKeyDownAsync(VirtualKeyCode keyCode)
{
return(InputSimulator.IsKeyDownAsync(keyCode));
}
public override void SynchroniseKeyState()
{
IsInEffect = InputSimulator.IsKeyDownAsync(KeyCode);
}
void HandleCapsLockKeyPressed(ModifierKeyBase capsLockKey)
{
_allLogicalKeys.OfType <CaseSensitiveKey>().ToList().ForEach(x => x.SelectedIndex =
capsLockKey.IsInEffect ^ InputSimulator.IsKeyDownAsync(VirtualKeyCode.SHIFT) ? 1 : 0);
}
bool IsShiftToggled()
{
return(InputSimulator.IsKeyDownAsync(VirtualKeyCode.SHIFT));
}