I have a custom form in my app, where a user can add a choice to the list of choices. To do this they click an “other” button which then shows a text box to type in the new choice.
I have it set so that when they click other this sets a boolean in the table, the other button then disappears and the close button appears, which when pressed changes the same boolean.
The issue I have is that the speed of setting the boolean value means one button will flash side by side when interacting with the other, before disappearing.
Do you have these conditions set up all in one button block or in 2 separate button blocks?
I’ve found that using separate button blocks allow for a smoother transition between actions, as opposed to turning actions off/on on buttons in a multi-button block.
I’ve tried both suggestions, the issue still arises. It must be fundamentally related to the speed at which glide can change the boolean value, since the different approaches you both suggested on the UI end do not resolve it.
Another option could be to make your own button using HTML and the rich text component. Put the code in a template column and use replacements to change the code on the fly
Ahh ok fantastic, I did have the custom action but didn’t realise we could use table data as labels. Thank you for this. And thanks to everyone for your replies.