Dynamically hide a button/object based on a field

[Bryce.dahle]

I think that the option to dynamically hide a button/text box/drop down/etc. would be incredibly helpful in Tulip development. It would lessen the duplicate steps you would need to have to have a button in the same place as another button, as well as removing having to redo any work you do to one step and needing to add it to the duplicated step.
The functionality is somewhat there already with the “enabled state” option, it could be reworked to either hide the object entirely or leave it there but not enabled

[thorsten.langner]

Also find discusstions here:

Keep custom widget from blocking click when hidden? - Developer - Tulip Community

Hide button on Steps, click on print button - Support, Troubleshooting, & Help - Tulip Community

Hide objects like single select - Support, Troubleshooting, & Help - Tulip Community

Hide button in tulip - General - Tulip Community

Enabled State on Inputs

Beside the fact, that it would be very useful, this would also be a step in terms of consistency. All inputs should have this function. It is only a logic to decide if you add the disabled attribute to the html-tag. Since tulip has this logic already built for buttons you should copy it to other inputs as well. And while you do so, also add the same logic for the hidden attribute as well. It is 98% the same thing! I really appreciate, tulips latest updates in those topics. But sometimes I w…

This is a frequently discussed feature. I wonder if there is really no request before.

I totally agree and think it could be relatively easy, since we already have the “disabled” on buttons…