Hi guys, hoping you can assist me.

I am evaluating your controls for a major project I am working on. Having a little difficulty with getting the AcceptButton event handler to fire. Here is some pseudo code from the code behind which outlines the scenario:



I have created an asp.net button in the footer template and included it's ID in the Dialog AcceptButton property.

What is happening is the further actions code is being run before the dialog is accepted. Specifically I want to set field focus on a textbox control after the dialog is accepted but this fails as the dialog still has focus when this code executes.

Here's some things I have tried:

1. Setting the AcceptButtonPostBack property to true but then the dialog doesn't disappear when the button is clicked.

2. Moving the further actions code to the button's click event handler but it doesn't seem to fire when the dialog button is clicked.

3. Displaying the dialog either server side through the InitialState property and also using the RegisterStartupScript to use the 'eo_GetObject(Dialog).show' function client side.

Am I missing something really obvious here? Hoping you can steer me in the right direction with this.

Many thanks

Darren

Hi there, thanks for your reply.

I followed your advice and cleared the AcceptButton property completely. When set like that, the dialog doesn't close at all and it doesn't appear to postback either. I dont think I've ever had it postback propertly. When the AcceptButton property is set to the button again, the dialog closes but it still doesn't trigger a postback. If I also set the AcceptButtonPostback property to true, again the dialog doesn't close at all and doesn't postback.

Apologises and I understand your point about the way I had written the pseudo code - it was just to show you what I was trying to achieve rather than me expecting the dialog to change the page life cycle. You're right about steps a and b being in different code blocks. One of the things I had tried was putting step b in the button's server side click event handler. I think because the dialog isn't posting back, this code is never firing.

However triggering the postback event from the button IS the behaviour I'm trying to achieve as I can catch the click event separately server side after the postback has occurred.

One thing I never mentioned on my first post is at the moment the dialog is part of a user control and other controls within this user control are using the MS AJAX extenders (watermark, validator callout etc). I had planned to use the dialog in a number of user controls similar to this. Do you think this could be a reason for what I am experiencing?

EDIT:

I have experimented further with this. Completely new page with basic button added to trigger the opening of the dialog.


Code Behind Click Event Handler


In this example, there is nothing in the page_load event. When Button3 is clicked the dialog appears. When the AcceptButton is clicked it now DOES postback. However, rather than disappearing it reappears after postback.

I have also tried loading the dialog at first page_load with the usual If Not Page.IsPostback etc... Again when the AcceptButton is clicked it still reappears after postback. Its like it's ignoring the IsPostback property.

So now I am really at a loss on what to do next. Any ideas guys?

Many thanks
Darren

Hi Darren,

Thank you very much for the update! This does make sense. All contents in the dialog still belong to the page so it does trigger all validation logic as if they were directly placed inside the page. As you have discovered, setting CausesValidation to false bypass this logic and allows the post back to proceed. I would expect setting ValidationGroup also work if you do need validation on the dialog contents.

Thanks!