@kastork I think I found a neat way to avoid the false positive invisible warning, committed now 🙂

@S You must never instantiate UIComponents yourself like you did with `RecordView1`/2/3 - this might seem to work at first, but you're msising out on important life cycle events, which will definitely bite you later.

@edvin thanks

@S I improved the

Slideshow

component, so your code can now be written like this:

@edvin uploaded a file: Slideshow demo

If you want individual timeout for the slides, you can add the timeout info to each slide, together with a transition. No timeout means you have to goto the next slide manually.

This is how you configure transitions and timeout individually:

@edvin uploaded a file: Untitled

I'm typing up a blog post on the timeout / modal dialog example I posted last week here. This version expands it by adding a heartbeat to reset the timeout anytime the mouse moves in any of the windows. Also, the direct calls to start the timer and to close the windows are replaced with events.

@carlw uploaded a file: Advance Copy of Timeout App

@carlw You won’t need runLater in the event callback, it is by default received on the UI thread. You can configure where the callback arrives for each event :)

You mean because it's on the FX Thread?

@carlw Yes, the eventbus pushes the callback onto the UI thread. Or did you need to delay the action even further?

Would you mind checking that for me if you get a chance? I kept getting a ConcurrentModificationException when I removed it

...tested on Ubuntu...testing on Windows right now

@carlw uploaded a file: w/o Run Later on Windows

That’s not because it was not on the UI thread, but because you modified the list while iterating. In that case, runLater might be a workaround, but we can probably find a nicer solution. On my phone, a bit cumbersome, but looking at your code now.

ok. thx

No, it will run in the same pulse if you fired on the UI thread and received on the UI thread as well. Need to run the code, was hard to understand on the phone only :)

Do you know where it iteration is coming from? I'm just calling modalStage.close()

Thank you all so much for helping me!

I'm having trouble with TreeView.populate

Looks like it shouldn't be called more than once

It adds listeners to supplied ObservableList's, but they are not weak and never removed

@aimozg where did you instantiate your listeners

I do not, the

populateTree

does

fun <T> populateTree(item: TreeItem<T>, itemFactory: (T) -> TreeItem<T>, childFactory: (TreeItem<T>) -> Iterable<T>?) {
    // add children to item and recursively call populateTree
    (children as? ObservableList<T>)?.addListener(ListChangeListener { change ->
        // if children is observable, hook to sync changes

I have a master-detail setup with a TreeView in detail pane

and I have new set of listeners added to every node in my model object when I select another object

right now I see no solution but rewrite populateTree to wrap listeners in WeakListChangeListener and store them somewhere

aside unused (because bound to detached TreeItems) listeners being accumulated, I had another problem