With both approaches the

item

in the model in my App is null

@User uploaded a file:

Then you're not running the code I'm posting here and starting the

IRCApp

class I provided 🙂

To avoid confusion, here is a complete example, with package declaration and imports. Remember to actually run the

IRCApp

class as your startingpoint.

@User uploaded a file: Complete example with validation

By the way, it would be null if you don't actually hit the submit button.

That's because that is what causes the instantiation of the item, see the

onCommit

function of the ViewModel.

My code is at https://github.com/Redrield/BetterIRC

And the TFX code is under ClientFrontend

If you wanna take a look at what I'm doing wrong

I updated the example above so there is a null guard for item, in case you never clicked submit before exiting the app.

https://github.com/Redrield/BetterIRC gives me a 404.

https://github.com/Redrield/IRCClient rather

Checking it out.

@redrield Ah, I see what's happening 🙂 Your calling

super.stop()

before you disconnect. That's problematic, because

super.stop()

actually cleans up the injection scope, so when you then ask for an

IRCClient

below it, you'll get a fresh new instance. Move

super.stop()

to the bottom and you should be golden 🙂

Yep, that works

Thanks!

@redrield I would also advice against using `lateinit`for your

ch

variable in

IRCClient

. If you didn't connect, it would be uninitialized, and you'll get a nasty error on disconnect. It's probably better to define it as

var ch: Channel?

. Then you can (must) do the null checks, and that will help you to handle the disconnect and avoid the error 🙂

Great, you're welcome 🙂

Oh, and remember to add the validation code, or something similar 🙂

@User uploaded a file: Untitled

How can I set the left of a BorderPane to a Fragment?

@redrield

left(MyFragment::class)

hm... seems my usage of Fragments is broken then

Cause this Fragment needs paramters

@redrield It can get parameters, but you should not use constructor parameters, you should use

by param

and send the parameters into the fragment when you

find

them.

@redrield Push your current code and point me to it, then I can try to rewrite it 🙂

@redrield You can also do

left { add(myFragmentInstance) }

if you have already instantiated it.

That is basically the same as adding the root, so you could even do

left = myFragment.root

if you like. I think that looks uglier though.

Alright