Fast Forward Type Writer Issue
Fast Forward Type Writer Issue
So ive been trying to implement typewriter anim for dialogue using enter keyboard button to continue the dialogue. I want to implement the continue button to skip the typewritter animation before the dialogue proceed to the next text. i've impelemented the enter keyboard button and the continue button fastforward method to the continue button. The problem is the fastforward method is working but it still proceed the dialogue text to the next text but it works fine when i use mouse to click the continue button. Is there any settings i need to apply for the keyboard button to work properly? i've also put the UI Button Key Trigger component to the continue button and set the key to "Return"
- Attachments
-
- pixel.PNG (55.53 KiB) Viewed 161 times
Re: Fast Forward Type Writer Issue
Hi,
Try removing or disabling the UI Button Key Trigger component, or set the Input Device Manager's Submit input (see below).
The Return key is almost certainly mapped to your EventSystem's Submit input. So the UI Button Key Trigger is clicking the button and the EventSystem's Submit input is clicking the button, resulting in two button clicks.
The UI Button Key Trigger component's "Skip If Being Clicked By Submit" checkbox is a little misleading. I've updated the tooltip in the next release to clarify. The component can't read the Submit input directly from the EventSystem because it doesn't know which input module the EventSystem is using. It could be using Unity's built-in input manager, or the new Input System package, or something else. Instead, to use this checkbox, configure the Dialogue Manager's Input Device Manager component > Submit input to read the same inputs as the EventSystem's Submit. The UI Button Key Trigger component will check if the Input Device Manager's Submit input is pressed; if so, it won't click the button.
Try removing or disabling the UI Button Key Trigger component, or set the Input Device Manager's Submit input (see below).
The Return key is almost certainly mapped to your EventSystem's Submit input. So the UI Button Key Trigger is clicking the button and the EventSystem's Submit input is clicking the button, resulting in two button clicks.
The UI Button Key Trigger component's "Skip If Being Clicked By Submit" checkbox is a little misleading. I've updated the tooltip in the next release to clarify. The component can't read the Submit input directly from the EventSystem because it doesn't know which input module the EventSystem is using. It could be using Unity's built-in input manager, or the new Input System package, or something else. Instead, to use this checkbox, configure the Dialogue Manager's Input Device Manager component > Submit input to read the same inputs as the EventSystem's Submit. The UI Button Key Trigger component will check if the Input Device Manager's Submit input is pressed; if so, it won't click the button.