Then you wouldn't have run into this issue, because setting item to null would be an actual change.

this is based on the usecase "create a new one"

I dont find it weird

OK, but if you never use the properties from the underlying JavaPerson, you don't really need a ViewModel. Let me check if we can add a reset or something for this use case.

well I was hoping for a view model that will support both, one that has no item (a new one) and one that has an item (update)

You can do this if you never assign to item, but want to clear the values after commit:

I know I know I ask too much

@User uploaded a file: Untitled

Not at all, I see the use case for sure 🙂

This one basically never touch the item property.

so the onCommit would contain logic to determine wether it is a new or an update based on the setting of the

item

It could, for sure.

Let's play with it and see how it works out and if it feels weird.

Leaving work in a bit, need to pick up the Surface Pro and eat, then I'll be back.

@edvin which keyboard will you be using with the surface pro?

@carlw POK3R of course 🙂 It came with Windows 8.1 so I'm about to upgrade to Windows 10 now.

@edvin don’t you have 2 or are you waiting for the second to arrive?

Doing Swing today... not as much fun as TornadoFX 😞

@jchildress Ouch.. my condolences 😁

@carlw I have two, waiting for the third. I forgot both at work today, I enjoy the MX Red version so much that I bring it back and forth, and the MX Brown version is always in the office. Need to get back, this is killing me 🙂

I just found out that it's not free to upgrade from Windows 8.1 to Windows 10 anymore. Bummer!

where did you order it @edvin?

ebay

the pok3r?

No, those I ordered from wasdkeyboards.com and mechanicalkeyboards.com + one from a guy in Israel.

It's really hard to come by new POK3Rs with PBT keycaps and MX Blue switches.

@User uploaded a file: and commented: @edvin

Gr....

double GRRR

they are either out of stock or way too expensive