Re: [qooxdoo-devel] Memory and disposing component

2008-10-04 Thread Matthew Gregory
Jean-Baptiste BRIAUD - Novlog wrote: > Hi, > > I'm using Composite layed out by Dock. > > There is a component in the north (its a menu but its not important). > > what happen when I add another component instance in the north as a > way to replace the old one ? It won't replace the menu, it

Re: [qooxdoo-devel] Memory and disposing component

2008-09-29 Thread Jean-Baptiste BRIAUD - Novlog
Thanks ! Its really clear. On 29 Sep 2008, at 11:45, Fabian Jakobs wrote: > Jean-Baptiste BRIAUD - Novlog schrieb: >> Hi, >> >> I'm using Composite layed out by Dock. >> >> There is a component in the north (its a menu but its not important). >> >> what happen when I add another component instance

Re: [qooxdoo-devel] Memory and disposing component

2008-09-29 Thread Fabian Jakobs
Jean-Baptiste BRIAUD - Novlog schrieb: > Hi, > > I'm using Composite layed out by Dock. > > There is a component in the north (its a menu but its not important). > > what happen when I add another component instance in the north as a > way to replace the old one ? > > If you add a second widge

[qooxdoo-devel] Memory and disposing component

2008-09-29 Thread Jean-Baptiste BRIAUD - Novlog
Any idea on that question ? On 26 Sep 2008, at 11:18, Jean-Baptiste BRIAUD - Novlog wrote: > Hi, > > I'm using Composite layed out by Dock. > > There is a component in the north (its a menu but its not important). > > what happen when I add another component instance in the north as a > way to re

[qooxdoo-devel] Memory and disposing component

2008-09-26 Thread Jean-Baptiste BRIAUD - Novlog
Hi, I'm using Composite layed out by Dock. There is a component in the north (its a menu but its not important). what happen when I add another component instance in the north as a way to replace the old one ? Will it remove the one I added before properly or do I have to do it myself ? Th