@JD Sorry, that was a bad description of the issue on my part.

bindChildren

expects you to return a Node that will correspond to the item passed in, right? The issue with calling

button()

is that the builder will actually be called on the flowPane and attached directly. What you want is simply to return a Button instance and have

bindChildren

attach it, so you must not use the builder. So

Button()

is just instantiating a button, while

button()

is calling a builder that will attach that button to the

Node

it's called on. This is a common mistake, and I can absolutely see why it's hard to get the distinction. It's on my screncast list to explain this in more detail.

Makes sense. Thanks

Np 🙂 This is an irritating issue and I don't see a way to prohibit this technically unfortunately. I see many doing stuff like

callFunctionThatAcceptsImageView(imageview())

. This will actually attach the imageview to the current Node as well as pass it as a function parameter. Problematic, but luckily easily fixed once you understand the builders and specifically when no to use them 🙂

is it possible to make a table without knowing what data/columns will be added?

^ unsure if this is good or bad

Good? maybe…

I think it is good. It does give the community the ability to fix many problems with JavaFX. The desktop and web have different targeted markets. There will always be a need for desktop applications. Likewise for the web. Many companies use JavaFX, but dont advertise. And there are many users who still prefer an application that doesnt require the web to run.

yeah, kotlinFX

@edvin rewrite? 😬

@thomasnield @pike CREATE TABLE dynamic_cols ( field1 : CLOB )

@edvin Wouldn't that imply creating a bunch of native stuff for many different platforms? macos, windows, ios, android, various x-window toolkits?

@kastork Maybe. Depends on how the decoupled JavaFX will end up looking I guess 🙂

Maybe a great big AWT dependency! 🙀

If we were to port javafx to Kotlin, would we be able to use controlsfx too? I think it's a great idea. We are probably a strong candidate to be stewards pushing javafx forward. Maybe we can likely use our learnings to port to Kotlin Native as well one day

@edvin uploaded a file:

@edvin uploaded a file:

that's awesome! you made a....?

Just tried to remove some material, make a hole, change tool and do a simple chamfering. Everything worked perfectly. So happy right now. Did the video show up?

yeah. those flexible arms look familiar. i have a set to help with soldering

@edvin function useCheckbox(editable = false) is giving problem "java.lang.RuntimeException: CheckBox.selected : A bound value cannot be set."

the editable = false parameter is not blocking the checkbox

@mariofelesdossantosjr Show me the complete class 🙂

@iari I'm not able to reproduce. Two options: 1. Post a complete project that fails for you so I can debug. 2. Stop hurting yourself and go with Maven 🙂 hehe 🙂

@edvin did 1. 😉

That was a bit too involved 🙂

All it needs is a big red button in the hole, and an engraved "Don't Panic" on the raised flat.

And instead of programming TornadoFX, today I made a tictactoe game 🙂

@edvin uploaded a file: