I couldn't find a direct answer to this question, and I haven't had any luck making it work either.
For example:
on "Page0.aspx", I have a RadWindowManager and a button.
When I click the button, a RadWindow is created and added to the RadWindowManager server-side.
Initially, the RadWindow loads "Page1.aspx"....from "Page1", I navigate to "Page2.aspx" (This is all inside the RadWindow)
Now, I click the button on "Page0.aspx" and it adds another RadWindow to the RadWindowManager.
My first RadWindow which should be showing "Page2", now goes back to its default page: "Page1".
I've messed with opening RadWindows client-side and that seems to do what I want to a limited extent.
But I want to be able to work with the RadWindows server side. Possible?
For example:
on "Page0.aspx", I have a RadWindowManager and a button.
When I click the button, a RadWindow is created and added to the RadWindowManager server-side.
Initially, the RadWindow loads "Page1.aspx"....from "Page1", I navigate to "Page2.aspx" (This is all inside the RadWindow)
Now, I click the button on "Page0.aspx" and it adds another RadWindow to the RadWindowManager.
My first RadWindow which should be showing "Page2", now goes back to its default page: "Page1".
I've messed with opening RadWindows client-side and that seems to do what I want to a limited extent.
But I want to be able to work with the RadWindows server side. Possible?
1 Answer, 1 is accepted
0
Cori
Top achievements
Rank 2
Rank 2
answered on 15 Mar 2011, 01:05 PM
Hello Sam,
Anything that happens inside a RadWindow on the client, like page navigation, does not get saved. Thus, the reason it reloads with Page1.aspx as the content, since that was the url it was initially set. I think the only way to solve your issue is to store the current url being used by the RadWindows in a hidden field before the user clicks the button and then reload that information back to the RadWindows.
I hope that helps.
Anything that happens inside a RadWindow on the client, like page navigation, does not get saved. Thus, the reason it reloads with Page1.aspx as the content, since that was the url it was initially set. I think the only way to solve your issue is to store the current url being used by the RadWindows in a hidden field before the user clicks the button and then reload that information back to the RadWindows.
I hope that helps.