@carlw Okay, well thanks for this conversation.

NP. feel free to let me know if you find something totally different. we don't have a lot of pride of authorship on the channel

I may just be wanting things to be a way they are not. I've gotten used to front-end frameworks like React and Vue where you set up an observable store and then that's the only thing you ever manipulate

those could be enhancements. tornadofx doesn't dictate a software architecture.

when i get a chance, i'm going to look into coroutines to provide a nice pattern for reporting progress or even getting a confirmation during a long-running process

you should see some hints of Flux in what i was suggesting earlier

Trying to catch up on the viewmodel conversation.

@kastork Changes to the backing item should absolutely update the viewmodel facade properties automatically. In addition, you can flush changes to the viewmodel facade properties automatically back into the underlying item's property if you specify

autocommit=true

on the binding. If this is not happening for you, you've either come across a bug, or your're doing it wrong 🙂

@kastork most likely the latter

I do use

autocommit=true

Does the autocommit part work for you? So

personModel.name = "new value"

also updates

person.nameProperty

automatically?

I'm checking if these things are covered well enough in the framework tests. If not I will add some more tests now.

The view isn't intended to be an editor, so I'll have to implement an experiment to see

Easier with tests I guess. Hang on.

We have this test, which I think is what you're talking about:

@User uploaded a file: Untitled

That covers the model to data object connection, I agree

But it's not working in your app?

One likely reason would be that you don't bind against your properties, but against the getters or something. Can I see a bind statement from your ViewModel?

yes... stby

Then there's an

observable

list of

Data

objects which back a table view

Where is the ViewModel for this class?

Or rather, how is it defined?

Along these lines

Change

column("x", Data::x)

to

column("x", Data::xProperty)

and you're golden.

By the way, this is not a ViewModel. That's an entirely different construct.

Check out Chapter 11 in the guide when you have time.

The reason this wasn't updating, was that the x column was bound to the getter in the

Data

class. No way to listen for changes in a getter.

I've been reading the guide non-stop for three days LOL -- guess I'm not paying attention to details.

The best way to learn these things is to play with it, and hit some roadbumps. That way you end up really understanding it, which makes the journey ahead much easier.