ContentURL to another aspx page, how to close dialog ...

160

Chad posted over 16 years ago

I would like to develop the popup window in a separate aspx page so that all the code is self contained here, however how do I close the dialog from a OK button or Cancel button that is contained within the separate aspx page?

Currently the examples show creating the popup window all in one aspx page, so the Ok button can call a local javascript click event and call Hide on the dialog control.

Thanks ...

Parents

95

Nasir posted over 16 years ago

I think I figured out a workaround now... Its to create an iFrame inside ModalTemplate section and throw in OK CANCEL buttons under the iFrame like this:

<igweb:WebDialogWindow ID="WebDialogWindow1" runat="server" Height="350px" Modal="True" Width="845px" WindowState="Hidden" InitialLocation="Centered" Movable="false">

<Header CaptionText="Add New Account">
<CloseBox Pressed="True" />
</Header>

<ContentPane BackColor="white">

<Template>

<iframe id="frameAddNew" runat="server" width="100%" src="SomePage.aspx?some=somethingelse" height="300"></iframe>
<input id="Button1" type="button" value="Cancel" onclick="DialogAddCancel()" />

</Template>

</ContentPane>

</igweb:WebDialogWindow>
Also assuming that you have the java function available on your page etc...
function DialogAddCancel()
{
oWebDialogWindow1.hide();
}
Cancel
Reply

Cancel
160

Chad posted over 16 years ago in reply to Nasir

Looks like you've got the right idea. You've got to call back to the parent page to some close function to close the dialog from another aspx page.

Parent page:

function btnShow_onclick()
{
var dialog = $find("WebDialogWindow1");
dialog.show();
}
function CloseDialog(){
var dialog = $find("WebDialogWindow1");
dialog.hide();} The ContentURL would OK or Cancel button would have javascript code with this line:
window.parent.CloseDialog();

I don't believe you need to create another iframe within WebDialogWindow, just set the ContentPane property of ContentURL and the control does all the rest for you.

Thanks for replying ...
Cancel
Reply

Cancel

Reply

95

Nasir posted over 16 years ago in reply to Chad

Thanks, works great. Except instead of using control name straight, I think using control ClientId will be a good idea especially if you are working with content pages:

function CloseDialog()
{
var dialog = $find("<%=WebDialogWindow1.ClientID %>");
dialog.hide();
}

This already bit me... so by using .ClientId it did the trick.

So now I have removed the iFrame and back to using the ContentPane/ContentURL instead. Super duper!
Cancel
Reply

Cancel

Children

No Data