Bummer I'd have to resort to overloading the renderer, but I guess if
that's what it would take.
Personally I'll just fall back to the three manual checkboxes and
putting the validation code in my clean method.
Thanks again Richard, glad you found a solution.
For those who wish to overload the
Hey Retro,
My boss managed to get this working so I can't take the credit but
this works and it's pretty useful. Basically, he's overriding the
widget renderer and making each "choice" a separate list item, giving
each "choice" it's own ID, making it much easier to use CSS to format
the choices i
Ok, well I took at look at the two links and they were pretty much the
same thing; just access to the choice list as text, not the checkbox
generator.
I was able to generate the checkboxes manually, but they break the
form system silently and just don't work (don't map to the usertype
object for
Thanks, Richard. I'll take a look at the links you sent and see if I
can't work something out. In the meantime I've dropped back to a
MultipleChoiceField. :(
I'll post my findings.
-R
On May 25, 9:03 am, Richard wrote:
> Hey Retro, I'm struggling with the same thing. I've found two
> interesti
Hey Retro, I'm struggling with the same thing. I've found two
interesting links which take two different approaches although I can't
get either to quite work (I think the template is just not seeing the
actual control but it's not complaining loudly). But it's quite
possible that you'll be able to
I'm using the CheckboxSelectMultiple widget in a MultipleChoiceField
and I need more control over where the field labels go and the field
themselves. So far this is the only field type I've had a problem
with. I've spent at least a few hours trying to find info on the web
to no avail.
I can't fig
6 matches
Mail list logo
