[CLOSED] Tab Panel loading synchronization

[vadym.f]

Well, it can be called anywhere after ExtJS resources scripts.

Generally, I meant to call it within an Update listener. As an attempt to avoid a scenario when Ext.ComponentMgr.all.length is 0.

Yeah, I tried that approach in hope to overcome the invalid object count. However, without setting a delay, Ext.ComponentMgr.all.length continues to report zero even if Ext.onReady() is placed inside the Update listener.

[Daniil]

Just in Ext.NET v2 the onReady scripts are executed according the queue they are registered. I though it works the same in Ext.NET v1. Never mind.

Then I would try with Delay="1" ("1" should be enough) for the Update listener. It should cause the main Ext.onReady script will be executed before the listener and all components should be registered in Ext.ComponentMgr.

[vadym.f]

Just in Ext.NET v2 the onReady scripts are executed according the queue they are registered. I though it works the same in Ext.NET v1. Never mind.

Then I would try with Delay="1" ("1" should be enough) for the Update listener. It should cause the main Ext.onReady script will be executed before the listener and all components should be registered in Ext.ComponentMgr.

This appears to be working well in IE9 and FireFox 14. It doesn't work in IE8. Maybe, the delay of 1 is not sufficient. I don't feel comfortable having to rely on timed-out actions here but it looks more and more like we're running out of options. Hopefully, my paradigm will work well enough most of the time.

[Daniil]

Yes, I always try to avoid any delays if possible.

If you will be able to provide a sample to reproduce the issue, we would do our best to investigate a possibility to avoid the delay.

[vadym.f]

Where does ResourceManager logically place a script registered on the server by means of RegisterAfterClientInitScript method? I've noticed that it gets appended to the Ext.net.ResourceMgr.init() stack, so would it be fair to state that it always gets executed when the document is loaded the first time?

[Daniil]

Where does ResourceManager logically place a script registered on the server by means of RegisterAfterClientInitScript method?

To the end of the function passed to Ext.onReady.

Example

this.ResourceManager1.RegisterAfterClientInitScript("alert('RegisterAfterClientInitScript');");

Ext.onReady(function () {
    // the script generated by markup and code behind
    alert('RegisterAfterClientInitScript');
});

I've noticed that it gets appended to the Ext.net.ResourceMgr.init() stack

Ext.net.ResourceMgr.init() call is separate. You could look at the Page Sources to check that.

so would it be fair to state that it always gets executed when the document is loaded the first time?

Yes, any script registered by the RegisterAfterClientInitScript method will get always executed on first load.

[vadym.f]

Thanks for clarification! What would be the correct call on the server that would register a script on a page level similar in timing to that of BeforeUpdate event handler? Is it RegisterBeforeClientInitScript?

[Daniil]

Where? On the page which is loaded? Or on the page which initiates a load request?

[vadym.f]

Where? On the page which is loaded? Or on the page which initiates a load request?

On the page that is loaded.

[Daniil]

Well, this page does know nothing about an BeforeUpdate listener of its loader.

I think you could try to use the RegisterAfterClientInitScript method or DocumentReady for your needs.