@thomasnield We have support for that with events, and I'm actually building support for that into the new Commands as well.

@thomasnield - sounds like the EventBus would be your friend here

Yeah property delegate. What would it look like with commands?

That was what I was thinking as well 🙂

I'll show what I'm trying to do when I get to work

@thomasnield OK, great. I'm interested to see the code that should result in the action being fired.

Awesome! Sounds like we have a use case to test with.

@thomasnield The Command pattern is pretty new to me, but what I have now is pretty close to C#/Xamarin, just a little less clunky 🙂

When I think about it I could also use an old-school Future

I'll share what I have in a moment

Sweet 🙂

Haha, trying to combine support for

ui

and

async

is fun:

@User uploaded a file: Untitled

I am using a block operator with RxJavaFX but it's hacky and ugly to do that

@User uploaded a file: Command Thread Magic

Take a look at this sample. In the Controller, the

hello

function is actually private. The only way to access it is via the

helloCommand

, which turns the action into a command, and configures it to always run on the UI thread.

The

Say hello

button is configured to execute this action, and it also binds it's

commandParameterProperty

to the String you can edit in the TextField.

The next button,

Call action off of UI thread

however, does an explicit

execute

on the

helloCommand

and passes in a parameter directly. This call is fired off of the UI thread, but the

hello

action will still fire on the UI thread because of the

ui = true

parameter passed to the

Command()

constructor.

If you remove

ui = true

and hit the

Call action off of UI thread

button, you will get an error say that you can't show the Alert because you're not on the JavaFX Application Thread.

Commands can also be configured inline if you want.

@User uploaded a file: Untitled

There could be a builder for this, you you would write

command<String> { println...

of course.

Actually, ad hoc commands like that probably doesn't make any sense.

@carlw I'm curious to hear what you think Carl - you have prior experience with this stuff.

@carlw Should commands have a title as well? If you assign a Command to a Button or MenuItem, it could provide the title perhaps?

I added it so we can see if it has any value.

I will commit it with an experimental warning so you guys can check it out. I might be on the wrong track here, need input.

@User uploaded a file: Command title

Just to be clear, the

commandParameterProperty

binding can be swapped for

commandParameter = some value

if you have a static value for the parameter. You could even pass it a property, so the input can change even without a binding.

I also added a SquareRoot calculation sample ala https://blog.xamarin.com/simplifying-events-with-commanding/