Then I don't need to specify alignment, the

spacer

takes care of it for free.

(Unless you want to align the trend numbers as well, but I just wanted to push them as far to the left as possible)

@edvin - finally got a chance to watch the ToDo walkthru - well done!

@gtnarg Thanks 🙂 Too bad I didn't catch that bug before though.

I like the declarative nature of javafx - but that is an example of where it feels like you have to work around it.

How to you mean?

Setting the item into the list to fix the bug - why doesn't javafx provide an explicit way to trigger an update event on the list?

It's imperative - but at least it wouldn't be a hack.

@gtnarg Oh, yes, I totally agree. There should be a way to fire an invalidation event.

I added the

invalidate()

extension function to observablelist by that suggested trick (setting the item at pos 0 again), but it feels dirty.

I could also add an

invalidate(item)

function.

For the use case in the Todo App, it's actually good that we trigger the invalidation explicitly, because we don't want to perform a refilter for every change while we iterate.

I need some advice I dont really understand what is currently happening 🙂

I have the following

@User uploaded a file: Untitled

selectedGroup isn an itemViewModel

@User uploaded a file: Untitled

this code is called with openModal from a contextMenu

the contextMenu is on treeview

the fire(createGroup(groupname.value)) is captured by

subscribe<createGroup> {
            repository.createGroup(it.groupname, selectedGroup.item)
        }

@User uploaded a file: Untitled

this is the repository.createGroup method

when I call this I get the stacktrace of stacktraces

and I think it is because a fire event is done while still in the code of a fire event? The stackstrace seems to indicate that the onChange is called twice

@User uploaded a file: Untitled

MainController.kt:58 is the selectedGroup.name.onChange

@edvin if you check the stackstrace you will see two invocations, the first one occurs when I press the ok button in the dialog

I think it happens because I am changing the item stored on selectedGroup

@ron is your onChange called before everything is ready? is it firing with a null value when you want it to fire only when the user has made a deliberate change?

Looks like it