The GUI designer is not able to handle invisible components right now. It is not
a trivial change. You have an easy workaround - setting invisible components
manally in the code.
*** Issue 114937 has been marked as a duplicate of this issue. ***
It is more than just making the component invisible in the GUI editor. We should be able to assign bindings to the
visible property as well. That is more cumbersome to workaround.
About binding, this should be done by inspector window. I agree that this must be done. Imagine the follow use case:
I had a form where just four buttons should be visible at the same time (following the business logic), but in design
time I have 6 buttons. I really wish to have the non default visible buttons invisible during the design because I had
to design the view for a specific video size, and have 6 buttons just make the visualization broken. I remember that
this was possible some versions before, but now it is no more possible and it is really sad.
Agreed. This should be considered a regression, I was pretty sure I had been doing it before.
*** Issue 156208 has been marked as a duplicate of this issue. ***
Perhaps we could have the 'visible' property similar to 'defaultCloseOperation' on JFrame, i.e. set to never write the value to target component, just remember the setting from the user. So the components would stay visible in designer all the time, it would be only a runtime setting.
It would be really nice Tomas.
Netbeans 8.1 still has this property missing.