Ernesto, Thanks for the quick reply, but maybe I haven't explained in an accurate way the problem. Please correct me if I'm wrong; I get that you're suggesting me to "disable" all the components after the user clicks on a link, and enabling them after the server sends back the response. Is it correct?
The problem I'm experiencing is than the first click is lost if the whole page is being refreshed. It seems that the client doesn't send the event to the server; I'm assuming it because our log of the DataRequestCycle doesn't print anythink. Thanks you again Ale On Thu, Oct 1, 2009 at 12:45 PM, Ernesto Reinaldo Barreiro < [email protected]> wrote: > Is blocking the page with a "veil" while refreshing a valid solution? That > way users could not click on links while the page is refreshing... > > Best, > > Ernesto > > On Thu, Oct 1, 2009 at 12:37 PM, Alessandro Novarini < > [email protected]> wrote: > > > Hello everybody, > > > > I've just subscribed to this ml, and even thou I searched past mails > about > > my problem, I couldn't find any hint. > > > > I have a page that's refreshing its components every n seconds using > > AbstractAjaxTimerBehavior. > > Among these components there's a list of links. > > > > If I try to click a link near the refresh interval, the request get lost > > because of the refresh. > > > > One of the solution I'm trying is to disable the refresh on the > > onMouseDown, > > and re-enabling it on the onMouseUp event, but this doesn't work as the > > first event stops forever the ajax method call (the refresh). > > > > Every kind of help will be really appreciated :) > > > > Thank you in advance > > Ale > > >
