Hey Tony and everyone
I updated DS from version 2.2.13 to 2.2.25.1 and ran into a pesky issue where, when I use a Gamepad to control the dialogue and get to a point in a conversation where the Response Menu pops up, the 'default selected response button' does not receive a "selected" event. (Note that this issue didn't happen before updating DS, and I also used my source control to revert my project back to before I updated DS to confirm it was working just before updating.)
I recorded a video showing what is happening - I tried to keep it short but wanted to show exactly what was going on, so it ended up being a couple minutes long:
Does my hypothesis of the Response Button being "selected" BEFORE its gameObject is actually enabled make sense? Could that be the underlying issue?
If so, any suggestions on what I could do? Is there is another way that I can notify my 'Diamond Icon' that the response button has been selected instead of the "Event Trigger" maybe?
Thanks a lot for any help!
Initial 'Selected' event for Response Menu not firing when using Gamepad
Re: Initial 'Selected' event for Response Menu not firing when using Gamepad
Hi,
Please try this patch:
DS_MenuPatch_2022-04-17.unitypackage
It appears to have been one of those undefined execution order issues in Unity UI. On one machine, the first button always raised the Select event. But on another machine it didn't raise the Select event for keyboard or joystick.
Please try this patch:
DS_MenuPatch_2022-04-17.unitypackage
It appears to have been one of those undefined execution order issues in Unity UI. On one machine, the first button always raised the Select event. But on another machine it didn't raise the Select event for keyboard or joystick.
Re: Initial 'Selected' event for Response Menu not firing when using Gamepad
Tony you are the man! It looks to be working!
Thanks so much for the quick help! We have a milestone due for our publisher this Wednesday, and I was hoping to get this issue fixed by then So your fast response is very much appreciated!
Thanks so much for the quick help! We have a milestone due for our publisher this Wednesday, and I was hoping to get this issue fixed by then So your fast response is very much appreciated!