8 Apr
2010
8 Apr
'10
10:16 a.m.
On 08.04.2010, at 10:11, Reza RAZAVI wrote:
At 09:03 08/04/2010, Norbert Hartl wrote:
Well, no. I forgot to mention that I used a PRWidget for testing. In PRWidget the
#context is cached. I think Lukas meant this.
What I expect is to create a new context by invoking
self context structure: ...
This new context is attached to an html anchor. When this anchor is pressed I would expect
that the context provided via goto: is active. Exactly this does not happen. I don't
need the old context it is just a test measure to see that setting a property has an
effect. But I would have expected that the old context message is set on the old context,
the old context is copied to a new one and the setting of the property with the new
context text should have overriden the old one.
Norbert
I don't understand your question.
Hi Norbert,
The default implementations of #context in Pier, which is *PRCurrentContext value*,
return the CURRENT context. In your case, the current context holds 'set on new
context'. So, the behavior that you are observing seems rather 'normal',
except if "your component store[s] the old context". This is what I understood
from Lukas' message. In other terms, what I understand is that if you need the
'old' context, it should be cached by your component.