If you can provide a minimal example that shows your issue and how you would expect the parameters to be passed I'll be more than glad to give it a try. I didn't yet have to play with nested widgets in tw2, so I'm more than happy to have a reason to do it :)
About the key option, is used to choose the name of the parameter and so pass it back and forth to validation. If a key is not provided the id is used instead. Should be fairly safe to rely on it even though it is not documented as it is the only way to name your parameters without having to respect the CSS ID regular expression (for example you cannot place an hidden input named _method to simulate request method as Sprox does otherwise). On Wed, Jun 20, 2012 at 10:47 PM, Christoph Zwerschke <[email protected]> wrote: > Am 20.06.2012 19:59, schrieb Alessandro Molina: > >> I don't know if this can be helpful to you, but TW2 decides the name >> of the parameters from the "key" option of the widget. >> By default this is equal to the id, but the key can be totally >> different so that you can name the arguments your controller will >> receive as you wish. > > > I cannot influence the name of the field with the key parameter. It's not > documented anyway, and from the source it seems to have something to do with > validation only. > > > -- Christoph > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/turbogears?hl=en. > -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
