The other component is simply:
renderContentOn: html
html text: (self context propertyAt: #forwardText ifAbsent: ['kein Text
vorhanden'])
Yeah, but maybe #context uses an old cached context? Can you check
which is returned from that method, "self context" or "ctx"? To me it
looks like "self context" is returned, because there are several tests
that set properties and copy contexts, and they pass.
Lukas
Norbert
On 8 April 2010 08:21, Norbert Hartl
<norbert(a)hartl.name> wrote:
I tried to do some tests about transferring data
via context from one page to another in pier. I did
renderContentOn: html
| ctx |
self context propertyAt: #forwardText put: 'set on old context'.
ctx := self context structure: (PRPathLookup start: self context structure path:
'/targetpage').
ctx propertyAt: #forwardText put: 'set on new context'.
html anchor
goto: ctx;
with: 'go'
On the targetpage there is a component that reads the property from the context and
displays it. What makes me wonder is that under any circumstances the text being display
is "set on old context". Even if I press the link "go". Why is that
so?
Norbert
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
--
Lukas Renggli
www.lukas-renggli.ch
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
--
Lukas Renggli
www.lukas-renggli.ch