Input lag when creating and removing widget button (Also can break player's input and potential memory leaks)

[UselessMouth (Richard Chirkin)]

My original thread with the issue:

[BUG] Huge input lag when using UI widget buttons — Also you can break player inputs entirely

So if you create buttons through Verse code, like in this tutorial, when you do something for button to appear, you wait almost 1 second (!) to be able to see and click the button. Same goes for button closing. When you click on a button for it to disappear you wait almost 1 second (!!!) before it disappears and player regains control of the character. I am 100% sure this huge lag happens because of these two functions: player_ui.AddWidget() # and player_ui.RemoveWidget() So I tried to use w…

Additional old threads:

Trying to change the InputMode := ui_input_mode.None

Hi I am tying to create an interactable Canvas that can appear and disappear with 0 delay I am saving already the Canvas in a map and I use it every time I need it. The delay is pretty low, but I need it to be 0 Canvas:=MakeCanvas() set AllAgentsCanvasUI[Agent] = option{Canvas} The only way that I found to get a perfect delay is using the functions Canvas.SetVisibility(widget_visibility.Collapsed) / Canvas.SetVisibility(widget_visibility.Visible) the problem is, you can not change player_ui…

Does anyone else find Verse UI really slow?

I have been messing around with different UI to create a shop in FN. I originally created a widget and dialog device but that has a few issues. Firstly, you can’t really change anything about the UI at runtime. Secondly, we are stuck with an extremely low 6 buttons (5 if you want to take one out for a exit button). These issues led me to the terrible verse UI code. The benefit here was that I could create more than 6 buttons and bind them all. What I did not expect was just how slow the UI is. …

Potential memory leak code to reproduce:

https://gist.github.com/MattRix/912fd98e498a3e653457986bd65e8f94