At the moment, we can only control parameters with an enable flag. I’d like to propose adding a separate visibility or display attribute to the Par class.
In some cases especially in sequence or block-based parameter setups, I start with a menu that determines which parameters are actually relevant for the rest of the block. While disabling unused parameters works functionally, they still remain visible and add unnecessary clutter.
Having a visibility flag would allow us to completely hide parameters that aren’t needed based on the current context, making parameter blocks much clearer and easier to use.
What I’m proposing is that visibility would be a strictly UI-level concept, with no impact on parameter behavior or evaluation.
Specifically:
Hidden parameters remain fully accessible via operators and Python
Parameters in expression / export / bind mode continue to evaluate and update normally
Callbacks still trigger as usual when the parameter value changes
Hiding a parameter would only prevent it from being drawn in the parameter UI. All existing logic and runtime behavior would remain unchanged.
To keep things flexible, this could optionally be paired with a node-level toggle (for example, Show hidden parameters, near the tag button) that allows to reveal invisible parameters when needed for debugging or inspection.
Since an enable flag already exists to control interaction and execution-related behavior, this visibility flag would be limited solely to decluttering the UI in menu-driven or context-dependent parameter blocks.
Hope this clarifies the intent.
(here is a use case exemple that made me think of this, in that case with only two blocks it’s kinda OK to only enable/disable parm, but i’m sure the readability can be quickly impacted with several more blocks )
