Can't you just let your controller remove those specific params? Like: this.ControllerContext.Params.Remove(keythatidontwanttopropagate)
Arjen Stolk ----- Original Message ----- From: "Yurii Urazlin" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, February 13, 2003 8:27 AM Subject: Re: [Mav-user] additional configuration for commands I have no problem with this. As for me, though behaviour isn't what is expected, the case is too uncommon to introduce new methods. Maybe there is a way to change behaiviour to what it should be without changing API? I don't see it, but maybe it's possible... Cheers, Yura. ----- Original Message ----- From: "Schnitzer, Jeff" <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> To: <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> Sent: Wednesday, February 12, 2003 10:10 PM Subject: RE: [Mav-user] additional configuration for commands > Ah, right now there is just one set of "params" and each place that > defines params (controller, view, transform) just adds to the pile. > Perhaps different behavior is desirable. > > It would be easy enough to split up the params collection into three > separate collections. This would change the ControllerContext interface > so that instead of setParam() it would have setControllerParam(), > setViewParam(), setTransformParam(), etc. > > Does this seem like a good idea to everyone? > > Jeff ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf [INVALID FOOTER] ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf [INVALID FOOTER]
