Element.Methods.Delete(i) vs project tree update

[Mike Pagel]

When using code like this

Code: [Select]

element.Methods.Delete(0);
element.Methods.Refresh();
the project tree is not updated. The element was of type Component and the method is still listed in the tree. However, the method is no longer part of the Operations dialog and reloading the model obviously clean up the tree as well.

Is there any way besides the very user-visible approach of reloading the owning package through RefreshModelView() to get the tree in sync?

Thanks,
Mike

[Geert Bellekens]

Did you try Repository.AdviseElementChange (long ObjectID)?

Geert

[Mike Pagel]

Hi Geert,

yes, I tried that. Both, on the owning component as well as with the deleted method's id (just for the sake of testing, even though a method is not en EA element). But it has no effect.

Mike

[Geert Bellekens]

And you tried a Element.Update() as well?

Geert

[Mike Pagel]

Yes, this is crashing if called on the deleted method.  :-?

[qwerty]

void RefreshModelView (long ID) — Reloads the EaPackage with ID matching PackageID, updating the user interface.

Try this with the package id where the deleted element is contained.

q.

[Mike Pagel]

As I said in the original post, this is quite intrusive, highly visible to the user and looses the current element, since the refreshed tree is collapsed.

I think this is pretty much a bug.

[Geert Bellekens]

It is a bug. AdviseElementChange  should do the trick without the need for a RefreshModelView

Geert