EA_OnPreDeleteElement recognize deletion to late

[2ben7]

Hallo,

i can need your help again. Would appreciate it.

What i have to do, to recognize a deleted element from the Repository ?
Im using EA_OnPreDeleteElement. But as the docu says, the event raises BEFORE it gets deleted from the Repository.

At the moment, i react for my plugin in this method. But if i do a SQL Query at the actual Repository(from the argument parameter list of the method), it is not always
secure, that the Element is still deleted from the repository.

How can i prevent this run condition ?
Also there is no EA_OnPostDeleteElement -EventMethod

[qwerty]

Not knowing your use case it's hard to tell. But it looks like you have to bite the bullet: poll the real deletion after a short time and react accordingly.

q.

[2ben7]

Yes i can explain the use case in more detail.
I have a control in my addin, which list all current diagrams of the model.

When i recognize, that there are one or more diagrams deleted
(even whole packages with several uncount diagrams inside),
i execute the fast SQLQuery("get all diagrams id`s or name from model")
to update the list to its current state.

I use EA_OnPreDeleteElement for this.

But as it seems, there is no valid reliable event, i can use to be sure, when Repository is really upated.

[2ben7]

Hi Paul,

but u forgot one nice problem ,
btw: i agree to what you said and i know the difference.

This event gets not triggered, if there are 2 diagrams in a Package. If i delete the package (which also result that the diagrams get deleted) i receive NO EA_OnPreDeleteDiagram event ->
EA_OnPreDeletePackage is triggered. So i don`t know which diagrams are updated.

So my great idea was to invoke SQL Query command again, but this result in the timing issues i described for my topic.

Yes, at the moment i use all 3 types of Delete methods.

Any ideas ?

A diagram is not the same as an element, you need to catch EA_OnPreDeleteDiagram for that  

regards,

Paulus

[Paulus]

(sorry about x-posting)
What you could to is to start a timer in a separate thread that triggers an update of the control.

Alternatively instead of a timer just set a reload flag and catch the EA_OnContextItemChanged event that fires after each EA_OnPreDelete... event when deleting using the project browser. i think it will get fired after the element is destroyed so that would be a good moment to check the reload flag and refresh your control  8-).

best regards,

Paulus

[2ben7]

thx in combination with ContextItemChanged, i could work it out !

(sorry about x-posting)
What you could to is to start a timer in a separate thread that triggers an update of the control.

Alternatively instead of a timer just set a reload flag and catch the EA_OnContextItemChanged event that fires after each EA_OnPreDelete... event when deleting using the project browser. i think it will get fired after the element is destroyed so that would be a good moment to check the reload flag and refresh your control  8-).

best regards,

Paulus