From: Chris G. <chr...@ms...> - 2003-06-22 19:15:35
|
I'm new to the product so please bear with me. Environment: 3.0 Beta/IE6 When using the addChild() method to move a dynlayer to another dynlayer = parent the elm and it child elements are first destroyed and then = re-created. Is there a reason for destroying the element layers? Also during this process child layers with images intermittently stopped = loading causing IE to spin until the image load timed-out. Is this a = known issue?=20 I modified the _remove method to stop the elm from being destroyed and = modified _create method to re-use the same elm.=20 something like the following: if(this.elm) { parentElement =3D this.parent.elm; parentElement.appendChild(this.elm); DynLayer._assignElement(this,this.elm); DynElement._flagCreate(this); } This considerably speeded up the re-draw process and seems to have fixed = the image load issue. Comments welcome? Bugs found: Is this the right place to post them? dynlayer_ie: setLocation and setPageLocation methods are broken. = setClass needs overriding Thx ChrisG |