Basically, the idea behind the RadWindowManager is to allow the users to create on the client multiple RadWindows with pre-defined properties, set in the manager. The manager's client-side API
allows the developer to easily get a reference to such RadWindows and to operate with them.
There are a couple of things however, that should be kept in mind when using RadWindowManager.
1. In case you have multiple RadWindowManagers on the same page:
- All RadWindowManager's functions (radopen, radalert, radconfirm, radprompt, GetRadWindowManager, etc) are always using the first rendered RadWindowManager on the page.
- Every RadWindowManager "knows" only the RadWindows that are declared in its Windows collection.
This means that if you have a RadWindow2 as a standalone control OR declared in RadWindowManager2, and you use something like radopen(myUrl, "RadWindow2");, radopen will use RadWindowManager1 and will open a new RadWindow with the settings taken from RadWindowManager1. To avoid that problem, when you have multiple managers on a page, you need to get a reference to the correct RadWindowManager first and then call its methods.
var manager = $find("<%= RadWindowManager2.ClientID %>");
2. Standalone RadWindow controls cannot be controlled by RadWindowManager - they are separate controls and are not affected by manager's settings.
I hope this helps.
the Telerik team