@chrbongardt uploaded a file: Step

@carlw I will do this in a controller, so I'm thinking something like:

I'd very much appreciate your help!

@edvin uploaded a file: DB Lifecycle pseudo code

that happens before onShown() ?

@chrbongardt Hang on, will read your code asap

thank you 😉

@carlw This will happen whenever the controller is first accessed. It can be done preemtively from app.start() if needed, even in a background thread.

not when it's injected?

@chrbongardt The issue is that your

PersonModel

doesn't have a noargs constructor 🙂

@chrbongardt It needs to have one, or the framework can't instantiate it, because it can't create instances of whatever constructor parameters you require right now

I see 😛

but how should I bind the property to the data class then?

@carlw Injections are actually lazy, so it would happen whenever the injected controller was first accessed if you don't do it preemtively. I think it would be best to preload to avoid hanging on the UI thread. Must try some scenarios.

@chrbongardt uploaded a file: PersonModel

@edvin who calls getConnection() ?

@chrbongardt That's completely wrong and will result in that you can never change the person 🙂

@edvin uploaded a file: Untitled

If you want, you can optionally pass in a person, or instantiate a default person if none was supplied (which would be the case for automatic injection)

I see

You need to use the ItemViewModel. Hang on, I will show you.

@edvin uploaded a file: Person model with default person

Oh shit, Okay

@chrbongardt Your code bound to a specific version of the person object, so even if you called

model.item = someOtherPerson

, the bindings would still refer to the old person.

I will do some more reading on the Model and it's validation.. I think I've read that part to quickly 😛

Sorry and thank you!

I personally never do this, I leave them blank, or just always create a default Person

Like this:

@edvin uploaded a file: Person model that always has a person

yeah, I see, makes sense