It doesn't make any difference. I already exchanged the usage of "self context" with "PRCurrentContext value" but without effect.At 10:16 08/04/2010, you wrote:
In PRWidget the #context is cached.
Yes, but the cache is updated upon a context change by:
PRWidget >> onChangeContext:
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.
I unfortunately don't have time to double check this right now, but am pretty sure that this is how Pier works.
It is not lost, it is the active one.I don't need the old context it is just a test measure to see that setting a property has an effect.
I'm not sure about your test setup, since your 'old' context is cached by PRWidget, and 'lost' upon the context change (that replaces the 'old' context, with the 'new' one).
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
In your first post on this thread, you also said "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?"
These two observations put together, would they mean that when the anchor is pressed, the current context is neither the 'old' one, nor the 'new' one? What do you get exactly as context then? (My understanding is that in any case it can't be the old one, since it is 'lost', as explained above.)