Contextual #call: issue
razavi at acm.org
Thu Mar 11 16:14:17 MET 2010
At 17:36 26/02/2010, Nick Ager wrote:
>The solution I've finally arrived at is:
>1) I've added a method to my custom kernel #editingEnvironment
>2) I've overridden #environment in PRPierFrame so that it now reads:
>| environment |
>(self context command isView or: [self context command isQuick]) ifTrue: [
>environment := self context structure environment
>] ifFalse: [
>environment := self kernel editingEnvironment
I'm testing a specific type of *quick* command (#isQuick returns
true). During their execution, triggered by PRContentsWidget >>
onAnswerCommand:, they call other components (via #call:). My
configuration is Ubuntu, Pharo, Seaside 3, and Pier2.
The execution goes on smoothly when triggered via the *commands*
toolbar. However, I'm experiencing an issue in the following circomstances:
1) When trying to switch the current template just before the start
of the execution, using the above method by Nick.
2) When launching the command via an internal link, and only if I'm
not logged in.
In both cases the execution stops by the error raised in
GRPharoPlatform >> seasideCallbackMarker.
It is difficult to characterize the issue since its somehow
contextual. But, it seems that #seasideCallbackMarker is sensitive to
the components that are present in the current Pier Context.
I'd greatly appreciate any feedback on this issue.
More information about the smallwiki