Re: [Webware-discuss] MultiSelectField - type of value

[Matt F. <mat...@gm...>]

Hello Steve.

I wouldn't dive into making your own mods just yet; we're hoping to
release a new alpha of FormKit in the very next few days; then, you
should be able to make a subclass (or more simply, a
Validator/Converter) to make it work the way that you want.

I've tried to answer some of your questions below...

P.S. There is a mailing list/google-group for FormKit; it's brand new,
but it's at
http://groups-beta.google.com/group/FormKit4Python

On Wed, 23 Feb 2005 14:13:58 -0500, Steve M <sjm...@fa...> wrote:
> But if one option was selected, f.value() is type string and is equal to
> whatever was selected, whereas if more than one option was selected,
> f.value() is type list, with members being strings for the options
> selected.
> 
> I find this unfortunate, or at least I can't understand why this design
> decision was made. Why doesn't f.value() always be a list (if not None),
> and just have one element (the single string) if only one option was
> selected?

I expect that we wanted it to be as close to possible to a non-multi
SelectField.

I see your point, and will bring it up with the other two guys that
are hacking on it with me. You're probably right.

If you need this feature in the next few days, I'd say that the best
thing to do would be to make a Validator/Convertor that always
promotes non-None values into a list, and add it to your Fields.