Contextual #call: issue
razavi at acm.org
Fri Mar 12 00:41:10 MET 2010
At 21:48 11/03/2010, Nick Ager wrote:
>If there's a mismatch between the environment used within a
>rendering-callback cycle that's going to confuse Seaside when it
>processes the callbacks.
That sounds a very good point too; thanks Nick!
I've to look at what happens more closely, since now I've some clicks
"lost", in the sense that when I push the command's link, its
execution is not visible, although launched. I know that the
execution is launched, since I tracked this down to
GRPharoPlatform >> seasideCallbackMarker (as said before, the
execution of this command includes calls to other components). It
appears that in theses cases, #seasideCallbackMarker finds and
returns a context, that of PRContext >> activationCallback. However,
the #call: remains ineffective in the sense that the control is not
passed to the new component!?
More information about the smallwiki