Mike,

Comments below.

On 16/07/2012 2:28 AM, Michael Spertus wrote:
> My item provider's getText method looks at many descendants
> (children/great-grandchildren/etc.). If the descendant is changed,
> however, the item's label is not updated. I have (sort of) worked
> around this by modifying the arguments used to create the
> ViewerNotification in DescendantClassItemProvider.notifyChanged, but
> this breaks encapsulation horribly.

It's an obvious problem, but we've not addressed this is a nice way. Do
you mean that the descendants themselves produce notifications to update
their ancestors?

That's the approach I too with EGenericType. But the
problem is worse there because the labels depend on non-containment
references (names of referenced classifiers and type parameters) and
that I didn't handle at all.
> Is there a recommended way of handling this?
The nicest idea I've heard would depend on notifiers producing
read/access notifications that would allow one to determine all the
objects accessed to produce the label and attach listeners to each of
them. E.g., some type of content adapter that listens to all objects
and some thread-local logic that notices the notifications during the
label computation. Eike and I did work on a design for read/access
notification, but it's highly invasive and would require modifications
to all list implementations and all generated models...