> > Hi Jason, > > > > you should not use "params" when you are working with widgets inside > > another widgets, this means you have a CompoundWidget and what you > > must use is "member_widgets" not "params". > > > > member_widgets works just like params but it doesn't handle > > callables automatically and you can override them only at init not > > render/display time, this makes sense since you're going to > > instantiate a widget during a request... > > > > http://trac.turbogears.org/turbogears/wiki/StatelessWidgets > > > > Ciao > > Michele > > I can't remember why we didn't do it like this before... Does > member_widgets play nice with fields=? No conflicts there? > > Jason
Sorry for not following up on this one for a while. I just realized why we didn't use member_widgets before. member_widgets doesn't make the widget accessible to the template by name. You people who autogenerate your form based off the fields that come in don't care about refering to specific fields, but us people who use custom templates and place each field by hand do ;) Jason
signature.asc
Description: PGP signature
