@edvin brainstorming here and looking at some c# code. what do you think of using action= or command= as an object assignment as in WPF MVVM? I don't see much value in having action{} and setOnAction{} especially since setOnAction() will be familiar to plain JavaFX developers ( 😬 ), even with the async
the WPF MVVM wraps up the function of a command with extra stuff like whether or not the command can be executed. If there were such an abstraction in TornadoFX, then you could do something like action=action(async=true) { // some code}
the control could not only fire off the behavior but also disable itself if the action weren't capable of being executed