Sweet! Are you happy with this or do you see any potential for improvement?

thanks @edvin

no this is perfect. I feel this is a much better way to use enableWhen

Great 🙂

The Kotlin 1.1 issue has been fixed and will be in 1.1.1 🙂 https://youtrack.jetbrains.com/issue/KT-16581

cool now lets hope they release that fast

Yes. I think we'll release 1.7.0 soon anyway to get rid of all Kotlin 1.1 upgrade issues once and for all, then switch to jvm target 1.8 in 1.7.1.

@edvin - was the table column resize functionality part of controls-fx or just the row expander?

@gtnarg Just the row expander. The SmartResize policy is not good enough to be included in controls-fx yet I think.

why not, it works very well

I'd like to clean it up a lot internally first 🙂

I have a new fun feature I just added, will create a small screencast and show you guys later today, because I need help with the naming.

Back in a few 🙂

ok

Not a knock against Slack -- the developer should be given a better sandbox -- but I found this interesting from a Desktop versus Browser discussion http://www.pcworld.com/article/3176203/security/slack-bug-paved-the-way-for-a-hack-that-can-steal-user-access.html?google_editors_picks=true

(I'm using the Desktop app right now)

I have a tableview for which the preferred height of one of the cells varies across rows, however it seems that all rows take on the same height. Is there a way to make the row take on the height of the highest cell only in that row?

Nevermind....my assumption about the behaviour across rows is wrong 🙂

@ron commented on @ron’s file https://kotlinlang.slack.com/files/T09229ZC6/F04AMNU8290: Can somebody proof read this?

@User shared a file: Untitled

@ron Fixed "wether", made the intro list parallel, some commas added for the longer clause, removed an extra "Now" that was repeated in the final code example lead-in Any kind of user oriented application, whether a web application, a mobile application or a desktop application, interacts with the user. That interaction is usually some kind of "fill in these fields please, so something can happen". KeepassFX has several such interactions. And of course they are implemented with tornadoFX builders. The nice thing about developing keepassFX while constantly talking with in the Slack tornadoFX channel means that usecases I encounter will very often result in updates in the builders. textfield(username).required() has the validator required(). Validators can only be used on properties that are part of a ViewModel(). Because of the validators, the code for the OK button can contain the model.commit function. This ensures that the code inside the model.commit block will only be executed when all the validators are happy. If you press OK button and the validators will decorate the fields that do not pass validation: Since this afternoon, there is another way of doing this. button has the function enableWhen and disableWhen. Now you can link this to the validation state. Now the OK button will only be enabled if all the validators are happy. The code looks like this:

thanks, what do you mean by “made the intro list parallel"

skip the parallel bit, the list was fine. i just pulled out the it's

ok, adjusted them

thanks

@ron very good... I hope to put one or two up this weekend... I have been super busy at work this week... no time to finish it.

@carlw I reached out to our JUG organizer yesterday and haven't heard back yet... I will keep bugging him.

blogging with hugo and markdown is so easy

quite happy with it