Hello Per,

Set EnableViewState=false for the RadWIndowManager that you are using - this should help you achieve the desired behavior.

Kind regards,
Georgi Tunev
the Telerik team

I tried setting EnableViewState="false" for both RadWindowManagers, in
the two different user controls, but it made no difference!

To make it simple, I'll call the RadWindow opened from control 1 for "A", and
the RadWindow opened from control 2 for "B":

What I've figured out, is that when opening A, B is never opened - even if it has been opened before.
Opening B always open A, if it has been previously opened.

Page refresh opens both A and B, but I've figured out why:

Both of the user controls have a section like this in Page_Load:

if (IsPostBack)
{
    var arg = Page.Request["__EVENTARGUMENT"];
    DoSomething(arg);
}

The DoSomething-methods will ignore the argument caused by the other control,
but since refreshing the browser, the last __EVENTARGUMENT is repeated,
either A will open (alone) or B (together with A).

I might have to go for something else than postback triggered clientside from anchors,
but the really puzzling part is why opening B always reopens A, if it's previously been opened.
Opening A never reopens B.

The RadWindows are added to the (empty) RadWindowManagers serverside,
and I've tried to set VisibleOnPageLoad = "false", but then the windows never appear
at all.

Anything else I've not thought about?

I finally realized that the RadWindow that kept popping up together with the other,
didn't have the "VisibleOnPageLoad="false" EnableViewState="false"" settings on its
RadWindowManager.

Now the windows only appear alone - but I'm still not able to avoid the reappearance of
the last opened RadWindow when the browser is refreshed.

Shouldn't EnableViewState="false" be enough?

Hello Per,

Basically, if EnableViewState is set to true, all RadWindows' properties that are set from the server will be saved in the viewstate and applied again on the next postback. I am not quite sure that I understand your setup completely however, so at this point I cannot tell whether there is a problem with that property or not. If you believe that there is a bug in this functionality, please open a support ticket and send us a sample project so we can investigate further. Of course if there is a problem, we will do our best to fix it right away.


Kind regards,
Georgi Tunev
the Telerik team