@edvin ah, looks like you missed

Platform.runLater

in new version of

runLater

@alexp11223 what's the delay for after the window is shown? will a plain JavaFX Task work better or is that just demonstration code

demonstration of course in real code it's in property listener

something like an auto-correct or code complete?

yeah. Showing some information about the entered text (code) which takes some time to compute, so cannot be done after each letter

Oups 🙂 Fixed runLater.

@edvin also looks like the timer thread still lives after running (the application doesn't exit after closing the window)

ronsmits and i had a timer thread going a few weeks back

(a slack thread)

@edvin if you look at the code i posted yesterday, i think you'll see the timertask cleaned up

I specifically kill the timer thread even made a blogpost about it

yep

@ron from Feb. 23 "These two syntaxes function equivalently. The both seem to keep a Thread running indefinitely, however, so you may find yourself calling System.exit instead of Platform.exit."

between timer() and Timer().schedule( timerTask...

End of project is end of June but I hope to go into testing in 2 weeks

@ron Deploying fully from the new Puppet setup?

And automatically building

the business probably learned a lot about its SW in the process

Git to Jenkins to Nexus to tomcat

They are more officially scared when I come in as I give them hell about their code

@edvin what would you think about having a view stack popping option for backwards navigation? Removing the view in

onUndock

doesn't work for this because

onUndock

gets called on any navigation, not just back.

also might be nice to have a way to remove the nav buttons from toolbar completely.

@alexp11223 @ron @carlw I made the timer thread a daemon thread. I think that should be enough.

If I was creating a code editor (especially using RichTextFx) I'd be inclined to look at ReactFx as it was designed specifically to deal with these types of issues. Another option is RxKotlin.

@gtnarg What kind of issues are that?

Code editing related issues like ignoring keystrokes for a certain period of time.

@kastork You can access the nav buttons via

workspace.backButton

and

workspace.forwardButton

. You can hide or remove them.

@gtnarg I think actually coroutines have special support for back pressure handling etc. It might be worth looking into.

@kastork I made

workspace.navigateBack()

public now.

@edvin that should do the trick, thanks