@carlw I'm more of a Maven fan myself. I just ran into another issue of trying to figure out how to use local images without a resource folder

@danielmcq are they the right names?

lol jk, I figured out the resource folder thing. wrong placement

I've had nothing but trouble with Gradle, so I'm sticking with Maven. IDEA support for Gradle has been spotty all along, and I haven't once opened a project without running into some kind of issue. I don't see any real benefit from it. and no real problems with Maven so I'm staying with it for now 🙂

@amanda.hinchman-dominguez What do you mean "without a resource folder"? Where are your images located? More importantly, where are they on the class path once you build your project.. have a look in the target folder and that should give you the exact classpath location pretty quicly, which would dictate the correct path statement 🙂

You don't need a

resources

folder, you can stick images together with your source files, but you'd need to change your build descriptor to copy them to the build folder, since you'd be parting with the standard location scheme. No big deal, and I've done it on some projects where I feel it's more beneficial to keep source and corresponding resources side by side.

@danielmcq Looking at your code now, noticed a few thing right away:

There is no need to add a list to the

observableArrayList

function.

val shapesProperty = SimpleListProperty<ShapeItem>(FXCollections.observableArrayList(arrayListOf()))

is redundant. Just do

SimpleListProperty<ShapeItem>(FXCollections.observableArrayList())

. End result is the same though. More importantly, you have a bug in

ShapeItem

. The constructor takes two parameters (name and path), but you just throw them on the floor, you don't assign them to your properties.

@edvin uploaded a file: Untitled

Once you fix that bug, your buttons will render just fine, even if you use

button(shapeItem.name)

instead of

button(shapeItem.nameProperty)

. Binding to the

nameProperty

would allow the button label to change if the shapeItem name property changes, but if you don't need that, you might actually stick with just

name

, as it doesn't create a binding and as such is slightly more light weight.

@danielmcq You should also be aware of that you're asking TornadoFX to evaluate the

bindChildren

statement twice at startup, since you're first binding towards an empty list, then changing the list by adding two shapeItems, so it has to reevaluate. Simply preparing the data before creating the view would fix that, so just swap these two lines so they look like this:

@edvin uploaded a file: Initialize data before showing the View

Of course if you were indeed not loading data from memory you should do that on a background thread, and then your GUI would reevaluate the children-binding twice, but then it's used as a feature 🙂 hehe

This is a slightly more idiomatic way of defining the test data by the way:

@edvin uploaded a file: Untitled

Quick question: Is there any difference between

button("click me").action { ... }

and

button("click me") { action { ... }}

. Because I have troubles with the 1st form together with

runAsyncWithProgress

. The 2nd form works just fine, but

button.action { runAsyncWithProgress { ... }}

seems to remove the parent node of button instead of appending a spinner to the text of the button.

Is this a bug, or am I using the builder wrong?

Can you add a code snippet with the usage which doesn't work?

@elexx uploaded a file: Untitled

ButtonBar expects button instance

button("Button 1") {
    action {
    ...
    }
}

will return a Button instance where as

button("Button 2 ").action {

}

will return the type from

action

(or

setOnAction

) i.e. void.

Not sure I can follow you. Adding the buttons works just fine. But when I click "Button 2" strange things happen. Let me screenshot it

@elexx uploaded a file:

Wait, adding buttons work fine?

Ah, I misunderstood the issue. I am sorry, I am still novice with Kotlin.

Thanks anyway 🙂

Hi all. First time with tornadofx so excuse me if this is stupid. I want to draw a list of circles:

world.actor.forEach { actor ->
                actorModel.rebind { actor }
                circle {
                    centerXProperty().bind(actorModel.x)
                    centerYProperty().bind(actorModel.y)
                    radius = 10.0
                }
            }

I don't quite understand how the model binding works (right now it prints them out with some default positioning). Given an ActorModel, and a list of observable Actors, can I re-use my ActorModel to display each?

It's very important to understand this distinction 100%, or you're bound to run into similar issues also

I'm having another issue with binding to list changes. Here's a small repro. I would expect to see "drew circle" printed 100 times, but it only happens once.

Where is this actor coming from, what library is that?