Thanks for investigating. I totally agree that this is worth looking into and 
it's worth a bug report. ;) I would be great if you could put your findings 
into a report for me. :)
Thanks,
Martin


Am 15.01.2013 um 15:17 schrieb Dietrich Streifert 
<dietrich.streif...@googlemail.com>:

> Am 15.01.2013 11:56, schrieb Dietrich Streifert:
>> 
>> 
>>> 
>>>> 3. Investigate why there are obviously so many
>>>> instatiations/destructions in this situation.
>>> This would also be a bug, together with bullet point 1. We need to 
>>> find a solution for the problem you described and 1, is a solution 
>>> which might help so solve point 3 but it is not certain that its the 
>>> only valid and best way to fix it.
>>> 
>> Yes i'm trying to find out where all those objects are generated. 
>> There seemed to be a lot of destruct calls to qx.ui.basic.Label where 
>> I have no idea where the instances are coming from.
>> 
> Back from investigations ;-)
> 
> The source of all this instantiations/destructions is the fact that 
> setting the visibility of a single table column (my table has 11 
> invisible columns) triggers a full recreation of all column header 
> widgets each time the visibility of a column is changed via 
> qx.ui.table.columnmodel.Basic.setColumnVisible.
> 
> This in the end invokes  method qx.ui.table.pane.Header._updateContent 
> with parameter completeUpdate = true causing all header widgets to be 
> destructed in method qx.ui.table.pane.Header._cleanUpCells.
> 
> The event which causes the qx.ui.table.pane.Header._updateContent call 
> is fired in qx.ui.table.pane.Model._onColVisibilityChanged:
> 
>     /**
>      * Event handler. Called when the visibility of a column has changed.
>      *
>      * @param evt {Map} the event.
>      */
>     _onColVisibilityChanged : function(evt)
>     {
>       this.__columnCount = null;
> 
>       // TODO: Check whether the column is in this model (This is a 
> little bit
>       //     tricky, because the column could _have been_ in this 
> model, but is
>       //     not in it after the change)
> this.fireEvent(qx.ui.table.pane.Model.EVENT_TYPE_MODEL_CHANGED);
>     },
> 
> Despite of the problem of having 11 invisible rows the TODO mark 
> indicates that this is something worth looking into.
> 
> 
> Regards
> Dietricht
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS
> and more. Get SQL Server skills now (including 2012) with LearnDevNow -
> 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
> SALE $99.99 this month only - learn more at:
> http://p.sf.net/sfu/learnmore_122512
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel


------------------------------------------------------------------------------
Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery
and much more. Keep your Java skills current with LearnJavaNow -
200+ hours of step-by-step video tutorials by Java experts.
SALE $49.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122612 
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to