PowerDesk Pro 6::
File Format: PDF/Adobe Acrobat - View as HTMLLayout Manager. – File Viewer. – Archive-File Support (zip, tar, gz, rar, z, jar , [etc]; self-opening .exe). – Encrypt/Decrypt/Destroy
http://www.pcig.info/uploads/Reviews/powerdesk2008.pdfHOME |
I am constantly removing / creating NestedLayoutPanel's which contain Grids, other NestedLayoutPanels, etc. Should I be worried about leaks since there is no destroy method that gets called on the Layouts, Regions and each Panel when I remove a parent NestedLayoutPanel (at least none I could find)?
Hi matjaz,
looking for exact this feature I read this thread and tried out your code! Unluckely I cannot get it to work. Perhaps there is s.th. wrong with my call:
[HippoRepos-dev] [13183] hippo-ecm/trunk/package/skin/src/main ::
LayoutManager) { // Ensure only one layout manager exists + ( function() { + var Dom .. LayoutUnit.prototype.destroy = function(force) { + if (this.
http://lists.hippo.nl/pipermail/hipporepos-dev/2008-August/011032.htmlHOME |
api: Interface XLayoutManager::
Description: central interface to query for, create, destroy and manipulate user interface elements which are bound to a layout manager.
http://api.openoffice.org/docs/common/ref/com/sun/star/frame/XLayoutManager.htmlHOME |
innerLayout.destroy();Following the usual samples innerLayout is the nested BorderLayout .
I call your code from .js -file after loading ext stuff. (1.1)
Firebug error :
this.el has no properties
Prototype UI Intro - SlideShare::
addMethods({ methodsAdded: function(base) { base.aliasMethodChain('destroy', ' buttons'); }, destroyWithButtons: function() { this.buttons.
http://www.slideshare.net/kangax/prototype-ui-introHOME |
News::
Fixed problems which occurred when FXIcon, FXImage, FXFont, FXCursor resources were being deleted AFTER closing the display; now the destroy() function for
http://www.fox-toolkit.org/news1.htmlHOME |
Thanks for any help in advance.
Mark
I was questioning the same thing.
I have nested layout with many content panels across regions.
I implemented my own destroy() methods something like: destroy: function()
{
delete this.panel;
abc.FilterPanel.superclass.destroy.call(this);
}
I used kalebwalton's (whose code is incorrect) idea of implementing this:Ext.override(Ext.LayoutManager, {
destroy: function()
{
for (var region in this.regions) {
var r = this.regions[region];
for (var i=0, len=r.panels.length; i
r.panels.itemAt(i).destroy();
}
}
}
});
Ext.override(Ext.NestedLayoutPanel, {
destroy: function()
{
this.layout.destroy();
Ext.NestedLayoutPanel.superclass.destroy.call(this );
}
});And now contentpanel's destroy() gets called.
Shouldn't Ext support this ?
FYI - I'm just going to do something like the following for the time being:
/**
* Destroys each Panel in all the BorderLayouts LayoutRegions
*/
Ext.BorderLayout.prototype.destroy = function() {
for(var region in this.regions) {
for (var i=0,len=region.panels ? region.panels.length : 0;i
region.panels[i].destroy();
}
}
};
/**
* Destroys the BorderLayout in the NestedLayoutPanel
*/
Ext.NestedLayoutPanel.prototype.destroy = function() {
this.layout.destroy();
Ext.NestedLayoutPanel.superclass.destroy.call(this )
};
 Where's The Advantage In Windows Genuine Advantage?
 Stocks Bounce After S&P Joins Bear Market
|
LayoutManager destroy function?