And it’s a pity

ObservableValue

is invariant 😞

i'll kotlin-ify a plain javafx example i have that doesn't something similar later (if you don't find a solution first). i parse a textfield that can contain ${}-like expressions for formatted messages using binding

Parsing is not a problem. The problem is that tree view doesn’t re-populate children when root changes (via binding)

Now looking at source, it’s just an imperative call, it listens to changes in children collection (if supported). I would expect it to capture lambdas and execute them when root node changes…

If I place

populate

inside

rootProperty().onChange {}

it works except for the first time

@orangy i had that problem too .. may solution was to add a changelistening to the root observable and run populate again

it needs too much code

@orangy the root changes if you comment out the populate()?

root changes even if I don’t comment populate, children are not populated after a change

@Nikky I was working on the ListView / TreeView. I'm planning on a blog post when I get the populate() working

Right now I have to introduce a functional value

childFactory

and use this:

rootProperty().onChange { populate(childFactory = childFactory) }
            populate(childFactory = childFactory)

Basically,

populate

should do that. It looks like declarative syntax, should behave like this.

atm i do this

@orangy are the root property's children treeitems?

the gui part of the program is still WIP and not even used anywhere.. just toying around with code atm

glad you got it working. i'm still holding out for an all-binding solution

i would prefer that as well

@carlw not sure I understand. I have a model (no UI types in it), some nodes has children (containers), so I wanted to bind them to TreeItem via populate.

yeah ignore the previous comment

@orangy you wouldn't believe what i was doing all morning

CherryMX switch bouncing

I suppose a hardware-only solution is out of the question @orangy?

hardware jokes aside, i use animation and timers to "slow down" the user input from transformations like you're doing. that is, if the user is entering 'c-l-a-s-s' you'll want to give them time to form 'class' rather than deal with an incomplete entry

Yes, this. So given

val scriptProperty = SimpleStringProperty()
val evalProperty = scriptProperty.objectBinding { evalScript(it!!)}

and

scriptProperty

bound to TextArea text, I want

evalProperty

to reevaluate only when

scriptProperty

didn’t change for, say, 100ms

I know it’s not a proper solution for slow

eval

, but for a prototype I’m doing it should work

Please excuse me my stupidity, but I’ve never used JavaFX before. I’ve heard TornadoFX is so great and easy to use, I decided to give it a shot 🙂

for that case, I'd kick off a timer when the textarea contents change. that timer will update a property for your tree update

there should be a flag to hold off secondary fires

Can I combine it with binding?