Hello,
I'm trying to make sense of the RadWindow/RadWindowManager relation. I see that there can be many RadWindowManager controls defined in one page (unlike the RadScriptManager/ScriptManager which requires one implementation). But I also see that we can implement the RadWindow either inside of the RadWindowManager or as a standalone control.
What is the advantages of using the RadWindowManager beside being able to apply settings defined on the manager to the window? Is it better to keep the RadWindowManager outside of the master page and define it where it is needed, or is it better to keep a global radwindowmanager, and have radwindow as a standalone control?
Thanks.
I'm trying to make sense of the RadWindow/RadWindowManager relation. I see that there can be many RadWindowManager controls defined in one page (unlike the RadScriptManager/ScriptManager which requires one implementation). But I also see that we can implement the RadWindow either inside of the RadWindowManager or as a standalone control.
What is the advantages of using the RadWindowManager beside being able to apply settings defined on the manager to the window? Is it better to keep the RadWindowManager outside of the master page and define it where it is needed, or is it better to keep a global radwindowmanager, and have radwindow as a standalone control?
Thanks.