Toolkit.getDefaultToolkit() rather

(I am using

import com.sun.javafx.tk.Toolkit

)

@loloof64 are you looking for the AWT toolkit?

No, definetily not

In fact I wanted to make my own cursor

But I was wrong

Toolkit not needed

Just Cursor(MyImage)

I managed this way 😄

@edvin Could you review this before I Tweet it? I was looking into some of the TornadoFX internals, specifically Kotlin stuff. Thx http://bekwam.blogspot.com/2017/03/lambda-style-in-torandofx-type-safe.html

@User uploaded a file: Untitled

@edvin @carlw @ron Well. I made the following workaround to work with immutable POJO. But I suppose there should be way to decreate the amount of boilerplace, especially in RestartConfigWrapper.

@edvin well my very quick try last night did not work, but I think it should have:

@User uploaded a file: Untitled

strangely enough it now works. The oncommit gets called. the new object is made

@borboss I understand the workaround, but would it not force you to write more validation code?

after the rollback() both the validators on the textfield decorate the field with the dreadded red triangle

@User uploaded a file:

they dont when I move the rollback out of the oncommit and into the button.setOnAction but then the fields are not cleared

@edvin why would I do this in the onCommit and not just in the model.commit {...}?

@borboss I don't quite understand why you went this long way around instead of using the pattern I showed yesterday? Ron's implementation looks more like how it should be done (even though it has some issues as well).

@ron You are not supposed to ever call onCommit. It will be called by the framework when you call commit!

@edvin that is not really why I am asking it

@ron Inside your

onCommit

callback you simply create a new person and call rollback. Why?

the work I do in oncommit I might as well do in the commit itself

its a poc 🙂 to play with to see how it responds the idea is to create a new Person, clear the input fields and make another one. In a real application you would probably add the newPerson to a list or database or something

@ron Do you mean by overriding

commit

on the viewmodel instead of overriding

onCommit

?

This is a working example:

no I can imagine doing

setOnAction {
                        model.commit {
                                 val newPerson = Person(model.firstname, model.lastName) 
                    }

@User uploaded a file: Untitled