Unfortunately, the code has to complete before the refreshed page is
returned to the user. Perhaps you could create additional controls so
that the application flows more smoothly? It's hard to visualize
without seeing it and understanding the process, but you probably need
to re-design the UI to take into account your workflow.
--Mary
On Wed, 19 May 2004 16:11:02 -0700, "Jo"
<(E-Mail Removed)> wrote:
>
> I wish it was that easy - B can (and in most cases will) be pressed before A. It could be pressed 10 times before A is pressed.
> ----- Mary Chipman wrote: -----
>
> Does A always get pressed before B? If so, then open the page with B
> disabled or hidden, and enable/unhide it in A's code.
>
> --Mary
>
> On Tue, 18 May 2004 19:36:02 -0700, "Jo"
> <(E-Mail Removed)> wrote:
>
> >Hi,
> >>I have a small (hopefully!) problem. I have two buttons on my web page and when button A is clicked, the code behind takes about 3 seconds to execute. While it's executing though, I don't want the user to be able to click button B. What I have found happens is that if user clicks button B while button A is still executing, the code behind button B will start executing straight after the code under A has finished, and there is no page refresh/reload in between the two executions - that is my main problem.
> >I have searched the web to try to find a solution but have been unsuccessful. Can anyone tell me how I can either make button B disabled in the middle of button A's code execution (so once A is clicked, disable B, refresh the page and continue with execution of code under A), or end all code execution once the code under A has finished (ie do not go on to code under button B if it was pressed)?
> >>Thanks for your help - greately appreciate it,
> >>Jo
>
>
|