[CLOSED] Bug on destroying callouts

Hello support

There seems to be a bug when you try destroy a component that has a callout component on it..

if you create a tree with a callout component that has a delegate on, the callout object is created and if the callout is just shown once it will destroy correctly..

but if the callout is not shown and you call destroy on the tree then the method "this.destroyCallouts();" is called, the method fails since "destroy" is undefined on the callout object, the objet seems to be a type of object and not that of a callout..

the codeline number is 189 in the minified version of ext.axd

Code:

---

this.destroyCallouts();
this.callParent(arguments);},
      destroyCallouts:function(){
if(this.callouts)
      {for(i=0;i<this.callouts.length;i++){
      var callout=this.callouts[i];
      if(!callout.isDestroyed){ //<-- this part is undefined aswell, it might be of the reson that the var callout is not of the type callout
          callout.destroyFromCmp=true;
          callout.destroy();  //<-- this part failed since the method destroy is undefined
      }
}

---

Best regards

Akpenob

Hi @Akpenob,

I believe you've already reported it before.
http://forums.ext.net/showthread.php?28491

Quote:

---

Originally Posted by Daniil

Hi @Akpenob,

I believe you've already reported it before.
http://forums.ext.net/showthread.php?28491

---

Thanks for the quick reply, but this is not related...

This i not the same problem, the one you referred to has been resloved.. :-)

This is when the parent component calls destroy to its collection of callouts,
while the other is when the callout component call destroy on it self.

The problem here is that as i pointed out in the code is that the object that are stored in the parent colletion does not have the method destroy on it

Best regards
Akpenob

Sorry. Yes, it is another issue. Could you, please, provide a test case?

Quote:

---

Originally Posted by Daniil

Sorry. Yes, it is another issue. Could you, please, provide a test case?

---

As of now no...

I will try to simplify an exsample for the test...

I will get the sample up and running tommorow as i do not have the time for today..

in plain text would be somthing like this...

Make a button that creates a treepanel.
make that panel closable and then attach a callout on it..
Close the treepanel, then push the button to create an new one (i assum the destroy method gets called due to the creation of the new treepanel)

if we do this in our application the bug/error appares as descriped :-)

After some attempts I could not reproduce. We would much appreciate if you provide us with a test case.