It sounds like the control that captures the event is not in focus. The first click gets the focus and the second click is the one that actually gets processed.
Been there, had that happen. ...Glenn On Fri, Aug 29, 2008 at 12:36 AM, Cerebrus <[EMAIL PROTECTED]> wrote: > > It's possible that the first click cancels out because the client > event handler does not return a true value. And in the same vein, the > second click manages to return a true value (because some global > variable has been set earlier). > > But I'm just guessing ! ;-) > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://cm.megasolutions.net/forums/default.aspx -~----------~----~----~----~------~----~------~--~---
