Some more on this, in DynObject.prototype.addChild there is a line:

if(this.created) c.create();

however the first line of DynLayer basically says if(this.created)return,

So in addition to my suggestion below should the line in
DynObject.prototype.addChild be changed to:

if(!this.created) c.create();

I might of course be on the totally wrong track here...

> Trying to make myself useful, so I'm having a go at migrating LoadPanel to
> DynAPIX. Out of the box it doesn't work, I think I've tracked down the
> reason why. LoadPanel has a method called reload, which basically removes
> itself from its parent then adds itself again (I'm not sure why, I didn't
> write it and it seems to work). What is happening is when the remove
> happening, the elm is getting set to null, but is created is
> still true. So
> when I add child again, because created is true, the elm is not being
> created again.
>
> I guess this is a bug? the old API set created=false in
> DynLayer.prototype.deleteElement.
>
> I just tried adding this.created = false; to
> DynLayer.prototype.specificRemove, it seemed to fix the problem.
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev


_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev

Reply via email to