<@U25U0KPFT> That could work, but he could just as...
# tornadofxe
edvin
05/28/2017, 10:42 AM@carlw That could work, but he could just assign it to something directly inside
runAsyncc
carlw
05/28/2017, 3:53 PM@edvin I like the ui method because you're certain when it's called. If you're counting on an atomic operation within the call method followed by a platform runLater it may not work as you expect. Ex connect() followed by a runLater that sets a connected Label
e
edvin
05/28/2017, 4:15 PM@carlw Yeah, if you rely on such a pattern you should. But if you simply set a property and the label is bound towards it, that wouldn't matter. Depending on what you're doing, but I think doing it in
uic
carlw
05/28/2017, 4:16 PMYou mean wrap up the property setting Code in a runLater within the runAsync?
e
edvin
05/28/2017, 4:16 PMNo, you can modify observable values outside of the ui thread, can't you?
c
carlw
05/28/2017, 4:40 PMDepends on who's doing the observing right?
e
edvin
05/29/2017, 10:58 AMI'm not sure. Even a change happens on another thread, the Node that is bound to this property seems to update OK.