You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reproducible in v4.3.stable.official [77dcf97], not in v4.2.2.stable.official [15073af]
System information
Godot v4.3.stable - Arch Linux
Issue description
InputEventAction with pressed set to true when sent through Input.parse_input_event() continues emitting as pressed until that event_index real key/button is released (or pressed then released if it was not pressed) or until window focus is lost.
This was not the case in 4.2.2, is it intended for action to remain pressed when sending fake InputEventAction?
If it is intentional, is sending another event such as the code below then the intended solution? By the documentation for InputEventAction.event_index, it reads as if it is not:
"The real event index in action this event corresponds to (from events defined for this action in the InputMap). If -1, a unique ID will be used and actions pressed with this ID will need to be released with another InputEventAction."
Actions are now tracked per event id (after #84685 and #84943) to improve their reliability. This means that to release an action you need to release all its assigned events.
Tested versions
System information
Godot v4.3.stable - Arch Linux
Issue description
InputEventAction
withpressed
set totrue
when sent throughInput.parse_input_event()
continues emitting as pressed until thatevent_index
real key/button is released (or pressed then released if it was not pressed) or until window focus is lost.This was not the case in 4.2.2, is it intended for action to remain pressed when sending fake
InputEventAction
?If it is intentional, is sending another event such as the code below then the intended solution? By the documentation for
InputEventAction.event_index
, it reads as if it is not:"The real event index in action this event corresponds to (from events defined for this action in the InputMap). If -1, a unique ID will be used and actions pressed with this ID will need to be released with another InputEventAction."
Steps to reproduce
ui_up
key (up arrow)InputEventAction
should be printed to console as well as continuous stream oftrue
until focus is lost orui_down
is pressed and releasedIf testing in 4.2.2, the
ev.event_index = 0
line will need to be commented.Minimal reproduction project (MRP)
43_input_event_action.zip
The text was updated successfully, but these errors were encountered: