Thanks

@User uploaded a file: Untitled and commented: @edvin even if I use this as main the NPE occurs... If I understood you correctly this should work?

@lutz Weird. Yes, that should avoid using any jni calls. This works fine in the IDE, right? You just get the exception when you run via javapackager correct?

@ron Thanks, but I'll host it at work so I have full control 🙂

@nakamin OK, cool 🙂 And strange!

Yes. via IDE everything works. If I build up the app as DMG, install it, and start it the NPE occurs.

@lutz Can you send me the DMG so I can try to install it on a mac locally?

@lutz A couple of tips for `TestView.kt`: 1. You can specify the title in the View constructor:

View("TestApp Title")

. 2. The root node can be built directly using

override val root = form { }

- no need for the with(root) thing in init 3. The textfield builder takes the property as an argument:

textfield(dataHolder.titleProperty())

- much simpler than first creating it and then binding towards the textProperty. 4. Instead of

addListener

you can just do

property.onChange {

. A lot less noise that way:

textProperty().onChange { create() }

A download link to the DMG file.

Thank you for the tips!

@lutz Great, let me see if I can find a Mac..

@lutz I got the same error. Checking some things now.

@lutz You are using some kind of mechanism to join all the jars into one, maybe the Maven Shade plugin or something like that. It seems to be configured wrong, so the resulting jar only contains classes, no resources from the original jars. You need to reconfigure the shade plugin or whatever is joining all the jars to one, or simply remove it. What do you gain from doing it like this when you package the app as a DMG anyway?

(To verify, unpack tornado-fx-app.app/Contents/Java/tornado-fx-app-app.jar and you'll see that the resources from the original tornadoefx.jar is missing).

@edvin Have you tried v1.1 with Tornado? How do you like features like DSL markers and coroutines ?

@voddan I haven't in a while, the last time I tried the IDE support was so spotty that I abandoned it. Maybe it's time to check again. I'll investigate coroutines and try to give feedback before it's finalized. DSL markers are quite interesting.

👍

Damn. Ok thank you very much! I will look what there is going on with the packaging.

@lutz Sweet 🙂 Let me know what you find. At least the mystery is solved 🙂 hehe

Strange, IntelliJ prefers

tornadofx.Stylesheet.Companion.button

over

tornadofx.button

for auto-imports. I even can't select

tornadofx.button

in the import context menu.

Maybe the import mechanism in IDEA 2016.3.2 or the Kotlin 1.0.6 plugin is somehow broken.

@hastebrot I am also using IDEA 2016.3.2 and Kotlin 1.0.6 and have never had that issue.

I assume you're just making a button in a View or Fragment?

I've updated to IDEA 2016.3.3 and now the issue is gone. At least IDEA asks me to import

tornadofx.button

instead of the stylesheet one.

Yes, in a

View

.

Strange

After the update of IDEA the index was not renewed. So, it can't be a problem with the index I guess.

2016.3.3 still gives me the Stylesheet imports... I just have been putting

import tornadofx.*

right away....