[Seaside] Updaters clicks and changes on (sub)components
ssastre at seaswork.com
Fri Nov 23 21:20:02 UTC 2007
I have some updaters that are evaluated when the user clicks
somewhere. This works just fine when the user perform a click on the hooked
The problem arrives when the user makes two quick clicks in it
instead on one. For most cases there is no problem at all but, if in the
callback of the updater exist some message that removes a children of the
updated component, then the second updater makes continuations complain
about not finding that children to receive the action.
Anybody has ideas on how to prevent this kind of problem?
More information about the seaside