disabling immediate direct call to loadingFinished() for selected tab seems to have no recognisable impact

and some widgets, eg. color-picker have problems with calling doLoadingFinished twice
This commit is contained in:
Ralf Becker 2014-10-13 09:07:23 +00:00
parent 8298fdefcf
commit 026347ba2f

View File

@ -236,12 +236,16 @@ var et2_tabbox = et2_valueWidget.extend([et2_IInput],
// We can do this and not wind up with 2 because child is a template, // We can do this and not wind up with 2 because child is a template,
// which has special handling // which has special handling
this._children[0].loadingFinished(promises); // disabling immediate direct call for selected tab seems to have no recognisable impact and
// some widgets, eg. color-picker have problems with calling doLoadingFinished twice
// (color input gets re-rendered second time after hitting [Apply], if color-picker is in a tab)
//this._children[0].loadingFinished(promises);
// Defer parsing & loading of other tabs until later // Defer parsing & loading of other tabs until later
window.setTimeout(function() { window.setTimeout(function() {
for (var i = 0; i < tabs.tabData.length; i++) for (var i = 0; i < tabs.tabData.length; i++)
{ {
if (i == tabs.selected_index) continue;
tabs._loadTab(i,promises); tabs._loadTab(i,promises);
} }
jQuery.when.apply(jQuery,promises).then(function() { jQuery.when.apply(jQuery,promises).then(function() {