pushed

Thanks

I would've noticed this at home, but I haven't actually loaded it up there yet

shame on me

should probably also get it into CI, even if it's just building

@beepdog The app started now. It's telling me you're friends with Thomas 🙂

orly?

oh yeah southwest

I am 😄

Actually met him prior to joining SWA

Hehe 🙂

Where is the empty listview? Is it on the main screen? (Haven't look at the code yet)

image.png

hmm, maybe I commited the "working part"

stand by

I think I did

because I added that updated time

hah

Okay, that was using the

graphic = cache {

logic that works, but I get weird duplications sometimes, so I think I'm doing it wrong

pushed to use the ListFragment that leaves you with an empty list

OK, great.

graphic = cache

must be used with caution - and it's not that easy to understand.. ListCellFragment will be better. Checking it now.

ah, yes

I'm probably using it in many places wrongly

the guide is not very warning of it

but that would explain the weird duplication problems I see and such

oki, gonna drive home, will be AFK for a bit

I will have a look at the guide

OK!

@beepdog I found your issue. In

JiraTicketModel

your are actually binding your fields to the

jiraTicket

that is passed into the constructor. This makes sure the bindings never update even when the ItemViewModel.itemProperty is assigned a new value. You are supposed to eithher bind to a property on the

itemProperty

, or use the new binding syntax where you only give it a property reference. The ItemViewModel.itemProperty is updated, but you never allow it to be bound to the fields of your model, as they are still bound to the instance of

jiraTicket

which was created in the constructor.

You made the same mistake in

JiraDataModel