Hi Steven
This is quite a typical issue, particularly if performance is not to great
over the network, ie, if things are going slow it doesn't always appear to
the user that something is happening, and they click again. I have addressed
similar problems as follows:
Buttons are slightly easier to deal with than hyperlinks, in that they can
be disabled when the onClick event is fired, either within the .net onClick
event (button.disabled = true), or by using a Javascript function (provided
your button is accessible within the DOM), which then subsequently calls the
required action of the button.
I quite often build subroutines to render my buttons, with the buttons
actually placed inside <divs> or <spans>. This way, you can use a JavaScript
call to hide or replace the contents of the <divs> or <spans> to remove the
button. This technique is especially useful for preventing double clicks on
Hyperlinks - which of course cannot be disabled in the same way as buttons.
For example you could have a situation like this:
<div id="button_div">Button goes here</div>
When the button is clicked, a javascript could be called that does the
following:
<script language="javaScript">
function myButtonOnClick() {
var objButtonDiv = document.getElementById('button_div');
objButtonDiv.innerHTML = "..You've clicked this";
//Do something else now, ie the action of your button
}
</script>
This code simply gets rid of the button as soon as its clicked and replaces
it with text (or a graphic of your button that is grayed out for example).
As it is no longer a button, it can't be clicked any more.
I don't have any code on me, but could give you a few pointers if I bring
the code back from work. Let me know if you need any further asistance. I
appreciate that I haven't given you a full solution as such but naybe I have
given you a few ideas about how you might tackle the problem.
Good luck
James Stoddern, Senior Developer
