Damn, that annoying. I'll delay integrating this at least for a while -
the current solution spreads too much knowledge in the wrong places. If
there really is no good way to do this in MVC, we'll need to at least
find a less offensive hack... 

For example, save the filter to fix in an instance variable. Yes, that
puts some state in the wrong sort of variable, but at least the code
tells the story, and in the right places.

A better solution, anyone?

Daniel

Ned Konz <ned at bike-nomad.com> wrote:
> On Wednesday 30 October 2002 11:50 pm, danielv at netvision.net.il wrote:
> > Hi Ned, just looked this over, it looks good except for one thing -
> > I wonder if the #perform:orSendTo: mechanism is the best place for
> > putting the code for switching filters on and off, especially since
> > this is implemented in a few methods already.
> >
> > Is there an MVC specific reason not to use #toggleFilterState:?
> 
> Yes, you can't pass arguments to a menu item in MVC, AFAICT (you're 
> limited to a single selector). So I ended up encoding the set/reset 
> along with the specific filter, and unpacking them in 
> perform:orSendTo:.
> 
> -- 
> Ned Konz
> http://bike-nomad.com
> GPG key ID: BEEA7EFE