Not really, but I got a workaround using javafx dropshadow

I doubt it, but is there a way to use functions to create fxml object injection?

@amanda.hinchman-dominguez uploaded a file: Untitled

nov 19, 2017 1:28:56 PM tornadofx.DefaultErrorHandler uncaughtException
GRAVE: Uncaught error
java.lang.IllegalStateException: component.javaClass.getResourceAsStream(resource) must not be null
	at tornadofx.ResourceLookup.stream(Component.kt:941)
	at tornadofx.ResourceLookup.image(Component.kt:942)
	at space.juans.views.LoginView$root$1$1$1$1.invoke(LoginView.kt:33)
	at space.juans.views.LoginView$root$1$1$1$1.invoke(LoginView.kt:21)
	at tornadofx.FXKt.opcr(FX.kt:454)
	at tornadofx.LayoutsKt.hbox(Layouts.kt:103)
	at tornadofx.LayoutsKt.hbox$default(Layouts.kt:99)
	at space.juans.views.LoginView$root$1$1$1.invoke(LoginView.kt:32)
	at space.juans.views.LoginView$root$1$1$1.invoke(LoginView.kt:21)
	at tornadofx.FXKt.opcr(FX.kt:454)
	at tornadofx.LayoutsKt.vbox(Layouts.kt:110)
	at tornadofx.LayoutsKt.vbox$default(Layouts.kt:106)
	at space.juans.views.LoginView$root$1$1.invoke(LoginView.kt:31)
	at space.juans.views.LoginView$root$1$1.invoke(LoginView.kt:21)
	at tornadofx.LayoutsKt.region(Layouts.kt:142)
	at tornadofx.LayoutsKt.top(Layouts.kt:135)
	at space.juans.views.LoginView$root$1.invoke(LoginView.kt:30)
	at space.juans.views.LoginView$root$1.invoke(LoginView.kt:21)
	at tornadofx.FXKt.opcr(FX.kt:454)
	at tornadofx.LayoutsKt.borderpane(Layouts.kt:128)
	at space.juans.views.LoginView.<init>(LoginView.kt:27)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at java.lang.Class.newInstance(Class.java:442)
	at tornadofx.FXKt.find(FX.kt:413)
	at tornadofx.FXKt.find$default(FX.kt:398)
	at tornadofx.App.start(App.kt:79)
	at com.sun.javafx.application.LauncherImpl.lambda$launchApplication1$162(LauncherImpl.java:863)
	at com.sun.javafx.application.PlatformImpl.lambda$runAndWait$175(PlatformImpl.java:326)
	at com.sun.javafx.application.PlatformImpl.lambda$null$173(PlatformImpl.java:295)
	at java.security.AccessController.doPrivileged(Native Method)
	at com.sun.javafx.application.PlatformImpl.lambda$runLater$174(PlatformImpl.java:294)
	at com.sun.glass.ui.InvokeLaterDispatcher$Future.run(InvokeLaterDispatcher.java:95)
	at com.sun.glass.ui.win.WinApplication._runLoop(Native Method)
	at com.sun.glass.ui.win.WinApplication.lambda$null$148(WinApplication.java:191)
	at java.lang.Thread.run(Thread.java:748)

I'm getting this whenever I use resources.image(), this was working fine until I rebuilt the project...

I've changed something at tornadofx.FXKt.opcr(FX.kt:454) in my last commit.

But I don't think thats the problem.

🤔

do you use the latest version of the project? (I don't know a lot about javafx and tornadofx itself, I'm only refactoring the Kotlin-code ;-))

Yes, I am (1.7.12)

@nimakro do you know what can be the cause of this error?

@Juan than my commit is not your problem, because it's in the snapshot... so then I can't help you...

@Juan Between which versions of tornadofx dose the problem occur?

I think I was in 1.7.11 when I wrote the parts using the resources thing, I did change it to 1.7.12 but never rebuilt until now

I was in 1.7.10*

I changed my tornadofx back to it, rebuilt, but it's still not working, @nimakro

Mhm could you create a little sample app were this error occurs?

alright

can you create a variable by loop?

@amanda.hinchman-dominguez uploaded a file: Untitled

@Juan The problem is that your resource relative to your class. That means your image should be placed resources->space->juans->view but currently you have one folder called space.juans.view. That's why it is not finding the image

create the right folder structure and it will work

You mean make space, then juans inside then view inside juans?

@amanda.hinchman-dominguez No, but you can access the fxmlLoaders'map of components directly. If you look at the implementation of

fxid

, you'll see that it basically does

fxmlLoader!!.namespace[key]

to get to components by id 🙂

@amanda.hinchman-dominguez Why are you using FXML by the way?

yes I am 🙂

It's a verbose uphill battle IMO 🙂

I agree completely. However, that may be the path I end up going with for just the metroTileBuilder; I can easily implement a drag-and-drop controller with fxml

@amanda.hinchman-dominguez That's not easier in any way because of FXML, in fact it's only more cumbersome. I think you're misunderstanding something fundamental.

I ended up using FXML to be able to quickly create a customizable gridpane layout