[Seaside] Navigate to component via anchor?

Ramon Leon rleon at insario.com
Wed May 24 23:12:07 UTC 2006

Disregard my previous, I didn't read your issue close enough before
hitting send.  If your main menu loads the mainArea with the existing
component each time, then you'll have the issue you're having...
Components remember their state.  Have your main menu load a new
component each time it's clicked, your problem should go away.

> -----Original Message-----
> From: seaside-bounces at lists.squeakfoundation.org 
> [mailto:seaside-bounces at lists.squeakfoundation.org] On Behalf 
> Of Ramon Leon
> Sent: Wednesday, May 24, 2006 4:05 PM
> To: The Squeak Enterprise Aubergines Server - general discussion.
> Subject: RE: [Seaside] Navigate to component via anchor?
> > 
> > Okay, I figured call isn't the right thing to do because 
> the call'ed 
> > component will retain control until it answers. Fair 
> enough. Now I'm 
> > back to the idea of setting the 'menu'
> > variable on the 'component' so that components could ask 
> the menu to 
> > do the navigation for them. Ouch! Somebody tell me there's a better 
> > way to do this, its not immediately obvious to me what to do here...
> > 
> > Thanks!
> > 
> > -Boris
> Small hint... You don't always have to say "self call:", you 
> can say "mainArea call:", and only that area will be replaced 
> by the called component.
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the Seaside mailing list