And what do you hope to gain with

circle { also {

?

The actor's just a data class with a couple variables

Ideally I'd print the circle at the actor's location. But I added the also just for debug logging, because I want to know how many circles tornadofx is drawing.

oddly if I put debugging in I do get multiple "drew circles" printed. Maybe I'm misunderstanding how threading should work here

Newish user of TornadoFX here, just wanted to say to all the authors: Nice job, thanks for creating this.

A file was commented on

Thanks @mstave 🙂

@crummy Can you post a complete runnable example?

sure, I just did here: https://stackoverflow.com/questions/50437833/why-does-my-tornadofx-observablelist-not-receive-updates

@crummy Hang on, I will answer the SO thread now.

sure, sorry to make you run around

Short answer is here:

@edvin uploaded a file: Untitled

I posted the answers. I basically wrote:

Some observations: Calling someList.observable() will create an observable list backed by the underlying list, but mutations on the underlying list will not emit events. You should instead initialize actors as an observable list right away. Access to an observable list must happen on the UI thread, so you need to wrap mutation calls in runLater. For people trying to run your example - you didn't include a stylesheet, but references one in your App subclass, so the IDEA will most probably import the TornadoFX Stylesheet class. This will not end well 🙂 The also call has no effect, so I removed it. I updated your code to best practices here and there, for example with regards to how to create the root node 🙂

wow thank you so much. I did swap out the styles class for the example and did not test that... oops.

Is there a way to listen for changes in a list from a plain data class? I suppose I could schedule some comparison between them

@crummy My pleasure 🙂 You can of course have an observable list in a plain data class, so I think I didn't quite get the requirements. Can you explain what you want to do?

If you don't want to/can't use observable lists, you can fire events to force refresh

I have a data class I don't control. I'll look into force refreshing, thanks again!

The trick will be to detect changes I guess. How you do that will depend on your use case. If you get stuck, post some code and we'll take a look 🙂

I assume tornadoFX is largely used to take changes from the UI and apply them to data via a model. If I update the data, will the reverse happen - i.e. will the UI reflect the changes?

fwiw i still like fxml and scene builder

with enough experience you can go from an ui in your imagination to the scene graph that creates it, but especially for complex layouts or for beginners, being able to visually manipulate containers is very helpful

box packing is complicated and i've watched some of my team struggle to learn

fxml is neither here nor there as a format, but a good visual builder can speed things up

I have another issue (that probably stems from my incomplete understanding of bindings). I am updating my object in the background, and have a textfield that is bound to the object via a model. But I don't see changes in the UI.

A file was commented on

@danielmcq Thanks 🙂 I'll try to be more active again, I've got some more time on my hands these days

@crummy Several issues here.

toProperty

creates a property, but that property is just initialized with the field value, it isn't connected to the field after the fact. You need to use observable properties to get updates, simple as that. As long as you make changes to the model though, that doesn't matter.