why not make it possible to do

selectedGroup.onChange

So whenever something changes you want a callback?

no only when the backing item changes

That's already supported. The ItemViewModel contains the item in

itemProperty

, which is observable.

So you can do

selectedGroup.itemProperty.onChange { .. }

Does that work for you?

I can of course add an

onChange

function on ItemViewModel, but it would just call forward to

itemProperty.onChange

.

this code in KPhoto was written with just viewModel, need to change that

no if itemProperty worksm no need to do that

It's very easy to change to ItemViewModel.

yeah six of seven lines 😉

👍

itemProperty.onChange works like a charm

Good. ItemViewModel to the rescue again 🙂

By the way, we got a PR that fixed an issue with the SortedFilteredList. It prevented manual sorting of the table columns earlier. Don't know how I missed it.

I saw that

I love observable values.

I was thinking about creating support for remotely synchronized observable values with pluggable transport. Default implementation would use WebSockets..

I need a use case. It seems so cool, but I just don't need it.. hehe

YAGNI

biggest thread to software projects

laters shoppimg time

Yes, so I'm trying to deem is necessary!

Anybody has a use case? 🙂 hehe

Going bowling, back in a few!

@ron I guess Mr. Jeffries never worked with a client who adhered to the WDYFIWYWIT principle : why-didn't-you-fix-it-while-you-were-in-there

Hehe 🙂

@edvin for your websockets use case...i started on a multiplayer checkers game that first found players and then was going to use websockets to coordinate the gameplay https://bitbucket.org/bekwam/fxcheckers-repos-1 Maybe you'll find this interesting? It's one of those half-implemented projects