Summary A UInputTriggerChordAction does not fire when the action it references (the "chording action") is mapped in a different Input Mapping Context with a lower priority than the IMC containing the ...
[Link Removed] From UDN, the steps for their repro case: Normal case: Frame N : AddMappingContext → bShouldBeIgnored=true → FlushPressedKeys → bDown=false Frame N+1: OS IE_Repeat arrives → ...
When two input actions are bound to the same "pressed" key in the same IMC & one is set to RebuildControlMappings, the input of the other will trigger indefinitely while the key is held down. ...
This is somewhat related to [Link Removed] Closed and was brought up by a [Link Removed] Setting the CVar input.bRespectIM ...
[Link Removed] The workaround is as I posted in the UDN, to override the viewport client or to make a custom slate input mapping to change this behavior. But, there is a bug with that unmapping/l ...
When using the Enhanced Input Context, the Input Touch Hold trigger does not reset correctly after releasing a touch input. Unlike Mouse Hold, which keeps firing Canceled events as expected, Input T ...
This is a speculative bug report from the user. The fix for this is to re-do the work of 31224705 but in a better way. The "bShouldBeIgnored" flag is being overriden by the previous mapping's va ...
In the Enhanced Input System, when using a UInputTriggerChordAction to define a chorded input (e.g., Shift + W), the automatic chord blocking system (UInputTriggerChordBlocker) only functions correc ...