And big delays are inappropriate, so I need to show to user result of his actions immediately (before server responded), but with no collisions between front and back

May be, having a list of operations to be sent on delay and method which would optimize appending and removing from list is one of the best solutions?

there's enough info in my example to handle this. an objectId exists which can be used to examine all the actions whether they have a backend presence of not. for example, 3 updates in a row for an object not in the backend would be consolidate with the objectId in the same say that 3 updates with a valid id

and the -1 id is used to decide between a create or an update

okay, will check out later Thanks in advance

@abhinay I looked at it briefly. Not much computer time lately, and so much to catch up on!

How can I, by selecting an object in listview, to go deeper like in mobile apps? Only by switching views from one to another and vice verse (when want to get back)?

@abhinay I commented on the JDK10 issue now. Thanks for getting the ball rolling on this!

@chickenfresh You can manually keep track of the view you left behind so you can switch back to it later. The Workspace does this for you, so use that if it fits the app you're making.

@edvin I'm working with a SimpleObjectProperty and am getting a compiler error when I bind. The error goes away if I declare the field as Property<> however

Is this something that a PR to bind{} can fix?

@carlw If you use the new syntax this won't be an issue 🙂

i thought that was the new syntax

this is definitely the old syntax: https://github.com/edvin/tornadofx/wiki/Properties

i'm looking at this from last year: https://edvin.town/

@carlw I mean the new binding syntax 🙂

@carlw

val completedBy = bind(Todo::completedByProperty)

that compiles for me

Sweet!

And it looks better 😁

@edvin I was putting together a navigation demo but am having trouble getting my ListView to update. I add a few items with a plus, double click, and edit the item. Returning doesn't update the UI and navigating to a new IVM clears the previous edit.

Checking

(I'll get some builders in the cellFragment too)

@carlw You don't have autoCommit on, and you never commit, so no values will be pushed back to the item

I'd use a ListItemFragment

-.kt

Then assign it inside the ListView:

cellFragment(TodoListItemFragment::class)

And commit by adding

todoItemViewModel.commit()

to the action of the

<

button

i'll try it again. i had a button at one point that explicitly called commit()

cellFormat

doesn't need help determining if the cell is empty or not, so if you keep the

cellFormat

, remove the

if( !isEmpty ) {

- it's not needed 🙂 The cell will be cleared when it's not in use