On Fri, 26 Sep 2008, Nino Saturnino Martinez Vazquez Wael wrote:
This is a potential pitfall if you ever will have two Ajax components
that can remove the ones behavior, if the user clicks the other while
loading then it's gonna complain. On the other hand im not sure what
wicket can do
sync doesnt help in the area one bit
Because wicket already does that for you
The problem is that just after 1 ajax call that replaces/removes/what ever a
component another 1 is already waiting and want to execute.
in 1.5 we have to have a hash instead of the id i guess and silent failure
when
I think it's already been taken care of.. IT's because the user clicks
on something that no longer exists..
Adriano dos Santos Fernandes wrote:
Nino Saturnino Martinez Vazquez Wael wrote:
Hi Guys
One of the major problems with the game are that if you click a
box(AjaxEventBehavior) while
Hi Guys
One of the major problems with the game are that if you click a
box(AjaxEventBehavior) while the heartbeat(AbstractAjaxTimerBehavior)
are in process you will get an error, since the box's component has
changed and no longer carries that behavior. I've tried to solve this by
adding a
Nino Saturnino Martinez Vazquez Wael wrote:
Hi Guys
One of the major problems with the game are that if you click a
box(AjaxEventBehavior) while the heartbeat(AbstractAjaxTimerBehavior)
are in process you will get an error, since the box's component has
changed and no longer carries that
