No announcement yet.
  • Filter
  • Time
Clear All
new posts

  • Isomorphic
    Yes, definitely intended behavior, components are intended to be able to move between layouts without being permanently destroyed! (consider drag and drop, etc).

    If you want the component destroyed, you can just call destroy() on it and this will also automatically remove it from the layout.

    Leave a comment:

  • Remove from layout, should the child/element be destroyed?

    I noticed that when I remove a canvas from a layout (layout.removeMember) that it is not destroyed, the global ID is still there. I can easily reproduce this. Is this intended behavior? Or can I set an option somewhere to take care of automatic destroy when an objects is removed from its containing layout?

    This is with a nightly build of 19th of july, chrome 13 on ubuntu.

    gr. Martin
    Last edited by martintaal; 1st Sep 2011, 01:54.