I also had a problem with another project's class, which shadowed one of the

javafx.*

classes in the imports context menu somehow.

I've seen this issue a couple of times myself. It's very irritating. It mostly happened when I pasted some existing code from someone into IDEA. I've never seen it happen when I just start a class from scratch and write. I wonder if we can make change the priority of the imports somehow. Hm..

One way to force the correct

button

would be to write

this.button

. That would only match the

EventTarget.button

extension function.

I can't imagine how confusing this must be for new users though 😞

It's a minor annoyance, but yeah for new users it might be more than that... maybe confusing... not sure what to say...

import tornadofx.*

works for me...

Yeah, I think I will mention that in the guide. It actually makes a lot of sense to import

tornadofx.*

because lookups for builders will be faster as well.

I'll see what I can do in the plugin as well. At least for generated files I'll make sure to add the tornadofx.* import by default.

@edvin One problem with

import tornadofx.*

for me is I like to use IDEA's smart code reformatting, and if less than 6 tornadofx imports are used, it replaces the

*

with the actual imports. Do you know of a way to force IDEA to always use

tornadofx.*

any time there are any tornadofc usages? (I don't want to change the setting globally as I like it, just for a given package like tornadofx)

@Ruckus I think it's possible to say that you want star imports for n number of imports for a given package, so maybe the plugin can configure this spesifically for the

tornadofx

package. Then it would never be a problem, since you need to import some subtype of

Component

to do anything TornadoFX related.

Checking.

Can't find the setting.

@User uploaded a file:

@edvin Is that what you are looking for?

But hang on.. it must be something wrong with idea when it doesn't even let you choose the tornadofx.button import?

@jchildress Thank you :))

Actually, I think it's the box below where it says "Packages to import with '*'". I added

tornadofx

and it does the trick.

@Ruckus Thanks... just did the same.

Sweet, so all we need is for the plugin to do this.

Can the plugin affect the user's code style like that?

OK, I'm going to watch The Blacklist and then see if I can make the plugin force this setting somehow.

I'm not sure. I hope so 🙂 hehe

Back in an hour!

I got to catch up. I haven't seen any of season 4 yet.

question for all you smart folks:

override fun show(property: IntProperty?) {
        with(myForm) {
            field(property?.header) {
                textfield {
                    bind(property?.observable(IntProperty::getValue, IntProperty::setValue))
                }
            }
        }
    }

property : IntProperty

is a POJO, with get/set for an

Integer

My problem is that the `bind`expression gives a Type Mismatch: Wants:

Property<Int!>

, Found:

PojoProperty<Int!>?

Is there anyway to make this binding work without going via a something like this (since `by property`can't be used for local variables):

var value: Int by property(0)
    fun valueProperty() = getProperty(ViewBuilder::value)

oh, actually - changing the signature to

show(property: IntProperty)

fixes it

@permalmberg Also, the

textfield

builder takes an observable as parameter, so you can do

textfield(property?.observable..)

directly.

@edvin right 🙂

I've located the

ImportSettingsPanel

within IDEA, still trying to figure out how it configures the star imports.

@edvin Actually, that doesn't compile

@permalmberg You're right, it requires a Property, not just an ObservableValue. I might be able to change that though.