-
-
Notifications
You must be signed in to change notification settings - Fork 237
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dialogic_default_action isn't respected by Centered Choices box #2411
Comments
Choices are buttons and that means they use the ui_accept action not the advance action so this is expected. However I think we might be able to add a setting to also use the input action additionally to the ui_accept action. |
It seems like when I click on the mouse it freezes up the whole choices box. This may because of the code below. Code: var dialog_advance_action_value: bool = true
func _on_button_button_down() -> void:
print("Pressing dialogic_default_action...")
# This one doesn't work. Use other way, as documented in action_press
# docs. Input.action_press("dialogic_default_action")
var action_dialog_proceed = InputEventAction.new()
action_dialog_proceed.action = "dialogic_default_action"
action_dialog_proceed.pressed = !dialog_advance_action_value
Input.parse_input_event(action_dialog_proceed)
|
What do you mean it freezes up the choices? |
They don't work anymore. But I do see it's on my end. Sorry! I'll solve it later |
Should I close this issue since you can just rebind ui_accept? |
The problem
Describe the bug
dialogic_default_action
isn't respected by Centered Choices box. So when I click on a button that I've assigned to this, it doesn't work.To Reproduce
Steps to reproduce the behavior:
dialogic_default_action
in the Input Map. I used CTRL.Expected behavior
It works with the new button.
Screenshots
If applicable, add screenshots to help explain your problem.
System (please complete the following information):
Solutions
Workaround
You could probably send a space input action when ctrl is pressed?
Possible fixes
Not sure.
The text was updated successfully, but these errors were encountered: