I come from Android and until a two weeks ago had no experience with JavaFX or TornadoFX. I have to say I am loving it so far.

nice 🙂 yeah I move between the two.

^ is something I am using a lot as well. Haven't found a cleaner way to make sure something runs on ui thread apart from using empty runAsync.

I use a runnable and an event bus for polling

the guide says to use runasync, unless you want to make your own FXEvent

Is your issue with running it in forEach?

nah, I'm just not sure if I can actually do it... tested, it worked 😛

Yeah it will but it returns immediately, so if you have a bunch of stuff in that list and the callApi is not smart it will fire everything at once pretty much.

yeah, that's fine for me... I literally need them to runAsync 😛

I want to list up my api endpoints, and just fire them all off and get the status of them.

If you just need to run something in the background then when done update UI the

runAsync {...} ui {..}

works well for me. Sorry no resources per se apart from https://github.com/edvin/tornadofx/wiki/Async-Task-Execution

@edvin what is the current status of integrating coroutines in tornadofx?

Does anyone know of a way to programmatically expand all the nodes in a tree-table view? My data gets loaded sometime much later than when the builder has created the UI and I want the load to also cause complete expansion when loading is done. I also want to have "Collapse All" and "Expand All" buttons. Is the answer here how you'd go about it? https://stackoverflow.com/questions/27166838/javafx-how-to-expand-entire-treeitem-on-button-click-event

@kastork I think that is the way to go. TreeView has no method to expand all TreeItem, so you would have to go through each TreeItem. Not sure if Tornado has a utility method for it.

Trying it now...

Seems to work. Recursion worries me a little, but I guess if things get so deep that recursion is a problem, you've probably got a bad design to start with.

exactly

I'm missing a fundamental bit of Kotlin knowledge heres. This will not compile - the message is "Type checking has run into a recursive problem. The easiest workaround is to specify the types of your declarations explicitly." Two questions: 1. What's the second easiest workaround? 2. What would I apply types to? (explicitly stating the type of

child

doesn't fix it.)

I'm guessing you don't want the

=

before the

{

@Ruckus uploaded a file: Untitled

yup

Also, if

this.isLeaf()

is true, there won't be any children to expand...

right

!this.isLeaf()

was intent

That makes more sense 🙂

Though you probably don't need that check. If there are no children, is it an issue if you expand it?

The

for

loop would just be skipped

I didn't check to see if

children

would be a null or an empty list

looks like it is an empty list

Fair enough