Yeah, I solved this by adding a veil over the "offending"
component(AjaxEventBehavior) so that it cant be clicked while updating
with the timer(AbstractAjaxTimerBehavior). And the one with remove got
solved by adding a new clean label instead..
Johan Compagner wrote:
maybe adding removeBehavi
maybe adding removeBehavior wasnt such a good idea afterall ;)
the problem with nino will not be solved i think with reversing it...
because what then? then it suddenly executes a behavior on position 0 that
inst really the behavior you wanted?
thats even more dangerous
It should fail like it
Well, you can reverse the order of behaviors. Unfortunately currently
in wicket behavior index identifies the behavior which doesn't seem to
be the most solid approach. Maybe we could do something better in 1.5.
-Matej
On Wed, Sep 24, 2008 at 1:26 PM, Nino Saturnino Martinez Vazquez Wael
<[EMAIL
Hi
Im working on something where I have an onclick AjaxEventBehavior and
also an AbstractAjaxTimerBehavior, the timer behavior can remove the
AjaxEvent. Sometimes I manage to fire the AjaxEventBehavior apparently
when it's removed but before the markup is updated because I get this
error:
