Oh, I see. No, I didn't enable it myself. So my fragment is definitely recreated by the JavaFX itself. (It would be cool to have just a bit on the info on hot reload somewhere in the docs, currently it's described by one GitHub issue and one PR AFAICT)

@ron I've committed the

filterInput

function and I'm pushing a snapshot to sonatype as well 🙂

I'll pull and test

@ron I did one more commit, made a boo-boo.

you made a change in nodes.kt? a big one (24 lines)

@ron Yes. But pull again, that test hurt my eyes. You can now do

filterInput { it.text.isLong() }

If long is too long and you want to test for something shorter, do

it.text.isInt()

instead 🙂

it.text.isInt or it.text.isLong does not exist

@ron You haven't pulled the latest version 🙂

@ron You're minutes behind head! 😎

as usual I cannot keep up with you

My bad 🙂

ROFL you cannot add fractionals

@ron What do you mean? You can't add decimal numbers?

nope you cant

you cannot add 10.5

@ron Sure you can, just adjust your filter to accept . as well.

@ron uploaded a file: Untitled

10,5 should pass the isFloat test ?

@ron Adding just the

isFloat()

text would allow you to PASTE a float. The decimal sign (, or .) to accept is up to you. You could get that from the locale if you need to.

I made sysProperty a float to test this

@ron The way this works, is that the callback is run for every input event, so a paste would include the whole number in it.text, while a simple key press would only include that single digit, so the . would be in it's own event.

hmmz does not feel very intuitive but I understand

it works but to be honest I am not a big fan of it

@ron uploaded a file:

@ron I guess that's what we have to work with for a textfield. You'd want to evaluate the whole input as well, for example only accept a single .

The

!text.contains(".")

checks to see if we already have a dot.

@ron You could also apply the change to a copy of what you have already and check if the end result would be a float..