Probably, I don't remember what all went into the change. @edvin would know better.

Okay. So in the

runAsync

do I have to use

success

if I want to change the UI elements?

If I understand your question correctly, yes.

@Ruckus yep, googled it already, polishing my solution now

Thank you!

Usage:

val evalProperty = scriptProperty.debounce(100.millis) { evalScript(it!!) }

Nice

@carlw pls don't miss my question ))

@orangy @Ruckus this one continuously polls and establishes the user as pausing based on two flags, ff1 and ff2. if they're equal, then the user hasn't typed in any new chars in 100ms. if they're not, then the bound property won't change

@iLobanov did i post this for you already? https://courses.bekwam.net/public_tutorials/bkcourse_tornadofx_selecting.html

@carlw seems missed the link somehere 🤔 Thx!

@carlw huh, isn’t it a little bit more complex than my debouncing function above? 🙂

@carlw That continuously runs and checks every <duration>, whereas the

PauseTransition

only runs when the user is editing, and only updates after the user has paused for <duration>.

that's good to know. i hadn't seen pause transition before

@Ruckus that's cool I didn't know about

PauseTransition

, wish I knew this way earlier

would have made timing problems with the UI a lot less crazy for me lol

@carlw @amanda.hinchman-dominguez The JavaFX `Transition`s are pretty slick. TornadoFX actually has a number of helpers for them if your using them for animation, but I've found them really useful for non-animation related problems as well.

I'm still a fan 😆

Is there something like

onChange

but that would call lambda on initial subscription?

@orangy Do you want

onChange

to be called just once?

no, I want it to be called immediately and then on every change

Of course I can write this simple function:

fun <T> ObservableValue<T?>.attach(handler: (T?) -> Unit) {
    handler(value)
    addListener { _, _, newValue -> handler(newValue) }
}

I am afraid, I do not know a short hand for it.

if you're not using models, one way could possibly be event subscribers, but that may be too much work for what you'd like to do

@orangy Unfortunately, that's the only way to go. There's no built in way to run listeners immediately when added.

it would be nice to be able to add an option for onChange to call a function on initialization - I might look into that after work

seems like you need a change to trigger an onChange

you can play with the initial value to force a change

I wonder why

populate

gets

childFactory: (TreeItem<T>) -> Iterable<T>?

and not

childFactory: (T) -> Iterable<T>?

as a parameter? Shouldn’t it operate entirely in a business domain, and use

itemFactory

to map to the tree?