Hi Yanni,

I would suggest looking at the references to PRCurrentContextHolder, specifically PRPierFrame>>withContextDo:.

Cheers,
Reza

On January 4, 2013 at 6:05 PM Yanni Chiu <yanni@rogers.com> wrote:
> On 04/01/13 2:21 AM, Reza Razavi wrote:
> > On January 4, 2013 at 4:29 AM Yanni Chiu <yanni@rogers.com> wrote:
> >> It seems that the menu is nothing more than a page with a list of
> >> structure links, and is displayed through a PRDefaultView.
> >
> > Yes. The page (menu) itself is displayed as a PRDefaultView, which then
> > searches for each of its outgoing links/Components in the current
> > Context. So, the problem may also be related to the Context too.
> > Replacing your Component with a Widget may provide a solution, since
> > PRWidgets keep a pointer to their Context.
> 
> Okay, the saved context in PRWidget seems to be the crucial difference. 
> Without using PRWidget, the context used to generate url's would be: 
> "PRCurrentContext value". I don't understand how a PRContext gets 
> associated with a Seaside session though.
> 
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki