In a concurrent application thought, it might be a good thing to avoid subtle bugs.

Oh, and another ting. For small collections, converting to a

Sequence

before iterating could actually be detrimental to performance. Using immediate operations allow the CPU to utilize it's cache and as well as other optimizations like prefetching.

I could probably rename those parameters to not use "range". That would make it reconcile without it making it less clear I think. I'll consider the immutable approach today. I did not know that nuance about sequences.

In a table,, if I have an object with a sub object, how do I access the sub object's values?

also, is there a way to auto count a table?

@pike I will update the guide with info if it's not there, checking.

#### Accessing nested properties Let's assume our

Person

object has a

parent

property which is also of of type

Person

. To create a column for the parent name, we have several options. Our first attempt is simply extracting the name property manually:

column<Person, String>("Parent name", { it.value.parentProperty.value.nameProperty })

While this works, it has one major drawback. If the parent changes, the list won't be updated. We can partially remedy this by defining the value for the property as the parent itself, and formatting it's name:

column("Parent name", Person::parentProperty).cellFormat {
    textProperty().bind(it.parentProperty.value.nameProperty)
}

It might still not update right away, even though it would eventually become consistent as the TableView refreshes. To create a binding that would reflect a change to the parent property immediately, consider using a select binding:

column<Person, String>("Parent name", { it.value.parentProperty.select(Person::nameProperty) })

Bind that to a label for example.

@edvin That is terrible news. I hope she is doing well now.

@abhinay She's doing a lot better now that we know what it is. Still paralyzed, but she's on a steroid coctail and will try acupuncture to speed up the recovery. Hopefully she'll be back to normal, or at least close to in a few weeks 🙂

@edvin Hope she gets better... Sorry to hear about that.

Thanks @jchildress 🙂 Fingers crossed 🙂 Normally it's not a serious condition.

@edvin thanks, I couldn't get the .select to work in my ide.

I hope everything works out edvin!

@edvin sorry to hear that, let me know if you need any help covering TornadoFX issues and stuff.

@thomasnield Thank you. We're mostly back on track, it just took the greater part of the weekend to get things sorted.

@edvin My best wishes that your wife will be fully recovered very soon. It it absolutely no problem. You help me so much all the time and I’m very thankful for that. When it takes some time this is okay. I still have so much to learn. You know, I jumpstarted directly with Kotlin and TornadoFX and never really worked with JavaFX, so there is still much to learn and enough to do to fill me evenings.

@dr.fornax Thanks. And good to hear. I hate leaving people hanging, but I just don't have a choice these days. Won't ever take on this much work ever again 🙂

@edvin I wish I will soon be able to give something back and probably support you a bit with the project

@dr.fornax Looking forward to that 🙂 As the project grows in popularity we need more hands primarily with answering questions and improving documentation. Feature PRs are also most welcome of course!

I think kotlin and tornadofx have a high potential an I look forward to be a part of it

There are still many questions I have and when they are answered I am happy to answer them to other people here

So probably you can answer me one general question to start with this. I have added a textview to my project and have a model with a string property. Now I also want to change the text view when I switch the user in the table on the left of my project. But I did not figure out the right way to realze the binding. I have no problem with the general property approach but how does this work in projects where I use no TornadoFX forms?

@User shared a file: TextView property binding

I introduced a notesProperty as SimpleStringProperty in my model. Probably someone has the essential hint for me. Thank I can bypass the time and try to work with my map and textfield until we have a solution for the other problem

Do you really want to switch the textview (i.e swap it for a new instance) or do you simply want to bind towards a property in that new contact object?

Hm, the recommended way. I think I would like to update the content of the view

I am not sure right now about the best practice to do this

I think binding would be nice