Function KeybdEventIsPhysical

source/hook.cpp:3200–3237

bool KeybdEventIsPhysical(DWORD aEventFlags, const vk_type aVK, bool aKeyUp)
// Always use the parameter vk rather than event.vkCode because the caller or caller's caller
// might have adjusted vk, namely to make it a left/right specific modifier key rather than a
// neutral one.
{
	// MSDN: "The keyboard input can come from the local keyboard driver or from calls to the keybd_event
	// function. If the input comes from a call to keybd_event, the input was "injected"".
	// My: This also applies to mouse events, so use it for them too:
	if (aEventFlags & LLKHF_INJECTED)
		return false;
	// So now we know it's a physical event.  But certain SHIFT key-down events are driver-generated.
	// We want to be able to tell the difference because the Send command and other aspects
	// of keyboard functionality need us to be accurate about which keys the user is physically
	// holding down at any given time:
	if (   (aVK == VK_LSHIFT || aVK == VK_RSHIFT) && !aKeyUp   )
	{
		// If the corresponding mask bit is set, the key was temporarily "released" by the system
		// as part of translating a shift-numpad combination to its unshifted counterpart, and this
		// event is the fake key-down which follows the release of the numpad key.  The system uses
		// standard scancodes for this specific case, not SC_FAKE_LSHIFT or SC_FAKE_RSHIFT.
		if (g_modifiersLR_numpad_mask & (aVK == VK_LSHIFT ? MOD_LSHIFT : MOD_RSHIFT))
			return false;
	}

	// Otherwise, it's physical.
	// v1.0.42.04:
	// The time member of the incoming event struct has been observed to be wrongly zero sometimes, perhaps only
	// for AltGr keyboard layouts that generate LControl events when RAlt is pressed (but in such cases, I think
	// it's only sometimes zero, not always).  It might also occur during simulation of Alt+Numpad keystrokes
	// to support {Asc NNNN}.  In addition, SendInput() is documented to have the ability to set its own timestamps;
	// if it's callers put in a bad timestamp, it will probably arrive here that way too.  Thus, use GetTickCount().
	// More importantly, when a script or other application simulates an AltGr keystroke (either down or up),
	// the LControl event received here is marked as physical by the OS or keyboard driver.  This is undesirable
	// primarily because it makes g_TimeLastInputPhysical inaccurate, but also because falsely marked physical
	// events can impact the script's calls to GetKeyState("LControl", "P"), etc.
	g_TimeLastInputPhysical = g_TimeLastInputKeyboard = GetTickCount();
	return true;
}


/////////////////////////////////////////////////////////////////////////////////////////