i'm not trying to drag a Node from the small/large modules but rather enough information for me to create a Node on the lefthand side

in your case, this might be nothing more than a moduleId

the gesture from right to left results in a drag that will let the left side know about the module being dragged and dropped. the left hand side makes sure it fits and adds it. then when you selected, it's a new unique node that can be selected for the lower-right properties keep an eye on Jim's project too. he's going to have a board with pieces

@amanda.hinchman-dominguez When a module from right panel is dragged to left panel, does it leave the right panel?

Quick question: The github site states the "compile" line to add tornadofx to a project. Do you want to add the line for a kotlin DSL gradle build file? (build.gradle.kts)

It works with a normal

build.gradle

file. Do you have a kotlin DSL gradle build file?

From the TornadoFX Guide. Should "`Node` type" read "`Parent` type" instead? A View contains display logic as well as a layout of Nodes, similar to the JavaFX Stage. It is automatically managed as a singleton. When you declare a View you must specify a root property which can be any Node type, and that will hold the View's content.

@abhinay Indeed, I do

@edvin is your datetimepicker from tornadofx.controls ported to tornadofx?

@ron No it's not. It doesn't let you pick the time, you have to write it. That's how I designed it and how I think it's most effective, but others might disagree. We could include it, but later create the option to display the picker as a spinner type time selector for example?

@javafxpert That's correct 🙂 Thanks, will update the guide!

Hm.. the gitbook editor is just hanging for me, will try again and update it later today.

There, done 🙂

@edvin just entering is good enough for now other question how do you feel about having a default value in a model

@ron I have no issues with default values 🙂

@edvin is there a preferred way to setting them?

@ron It depends. If the defaults are globally hard coded, I usually put the default values in a companion object and chuck them right into the observable:

val ageProperty = SimpleIntegerProperty(Person.defaultAge)

hmmz the model bites me again

@ron uploaded a file: Untitled

As the item in the viewmodel is null so is the entry.time 😞

Hey @edvin, just noticed a small thing on IDEA plugin: in your settings page Languages & Frameworks | TornadoFX there is a help link about property delegates. The link currently leads to non-existent "Appendix A" (https://edvin.gitbooks.io/tornadofx-guide/content/Appendix%20A%20-%20Supplementary%20Topics.html#alternative-property-syntax), but the content is actually located at "Property delegates" section (https://edvin.gitbooks.io/tornadofx-guide/content/part2/Property%20Delegates.html#alternative-property-syntax).

@r4zzz4k Thanks, will update the link and do a release of the plugin soon, just need to fix one other bug.

@ron Yeah, there is no way it can extract that default value, so you'd have to set that in the model I guess. We could even add a parameter with a default value to bind perhaps?

@edvin that would be a good thing, I can imagine a lot of usecases with it

@ron Me too, come to think of it 🙂 Hang on, doing the plugin first.

OK, plugin updated and bug squashed 🙂 Need to put some kids to bed, then I'll look at the default parameter Ron.

@ron I've pushed a new snapshot (tornadofx-1.7.15-SNAPSHOT) which contains a

defaultValue

parameter for

bind()

. Let me know how it works for you, OK?

I will pull and test it

Exciting 🙂 I hope it works as intended, that's a really nice feature to have. It passed all tests, and I messed a little with it in the CRM.

it works