On Mon, Aug 27, 2012 at 3:54 AM, Melvyn Sopacua <m.r.sopacua@gmail.com> wrote:
On 27-8-2012 1:21, Nicolas Emiliani wrote:That's because the widget is merely the piece that get rendered. It's
> The thing is that the GridWidget.__init__ method does not get executed
> each time I access the form that contains it, so if the queryset changes the
> widget gets 'obsolete'.
driven by the form field and the form field should be the one managing
the available choices.
I see ... since the field also has the queryset I can make it reload the multi widget
_widgets and that should fix it, that way responsibilities seem to be pretty clear to.
Thanks!
--
Melvyn Sopacua
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Nicolas Emiliani
Lo unico instantaneo en la vida es el cafe, y es bien feo.
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
No comments:
Post a Comment