@edvin I mean the name...make it a condition rather than a property: disableWhen, enableWhen, etc (I'm writing some java.util.Optional stuff today)

@carlw That makes sense. That will atleast give a hint about that you need to return a property and not just a boolean value.

nvm I already changed that

@edvin follows the functional / fluent trend

@edvin "if" is an alternative too but JavaFX uses the When class

@carlw Are there more properties we could do this for?

looking over some code 👀

I did something wrong. StackOverflow 🙂

@edvin that looks like a good set. I sometimes remove and add back an entire component when hiding it for layout purposes. This keeps gaps from forming in the UI if there is a conditional display element. Maybe a removedWhen?

Found the bug 🙂

@edvin There isn't a specific property for what I'm describing.

Oh, that would be nice. But it might be hard to reclaim the same space in the hierarchy? Should we put in some 0.1x0.1 px Node in it's place or something?

I like this! It makes these kind of things declarative.

I could just check the index position of the node and try to inject it back to the same index?

That could be a total disaster if the hierarchy changes though.

@edvin maybe try it for something structured like fieldset which is grid-based?

That's another thing to think about. Depending on the parent container we need to do different things. We could of course support all the native containers.

you mean like this:

fun toggle() {

        if (root.isVisible) {
            root.isVisible = false
            accordion.removeFromParent()
        } else {
            root.add(accordion)
            root.isVisible = true
        }
    }

Yes, but if accordion is last in the child list of root, you'd remove it from the bottom and readd it to the top.

Probably not what people would expect.

no, in this case I am certain that accordion is the only child:

the full class:

@User uploaded a file: Untitled

@edvin the functional requirement I'm suggesting is like a "visible, but reclaim the space"

so maybe a 0 pixel thing

If we add a 0 pixel thing we can even get it back to the same space if the hierarchy changes while we're hidden.

yeah. i happen to mess with the hierarchy in my code for this case. But that's because I know where the Node will be returned.

I have a general idea of how to do this, will post some code in a min.

@User uploaded a file: First draft for `removedWhen`

This is what I'm thinking. @carlw what do you think would be a good Node to use as placeholder? I just created a Region for now.