Better handling of observer exceptions

[Benjamin Kampmann]

Currently we are getting als exception that observers raise on changes of the ObservableList.

That's bad, because the warning we are given is not very precise and so it is bad to debug this part of the code...

We have to find a way to get the exception and the whole traceback and not stop the process of updating the other observers...

[Florian Boucault (fboucault)]

Does it still annoy you?

[Benjamin Kampmann (benjamin-fluendo)]

it's really bad for debugging: YES!

[Florian Boucault (fboucault)]

The question was: "Is the bug still present?". I take that as a yes.

[Florian Boucault (fboucault)]

cf. [https://code.fluendo.com/elisa/trac/changeset/3715]

[Benjamin Kampmann (benjamin-fluendo)]

you just removed the exception handling? That is not good, because of ticket #386. We need a better way to catch them and not crashing elisa.

For now, I would say it is more userfriendly to catch all and let elisa go on working...

[Florian Boucault (fboucault)]

This will be handled Elisa-wise by https://code.fluendo.com/elisa/trac/ticket/630

[Benjamin Kampmann (benjamin-fluendo)]

k