> I'd actually suggest that you create a composite element that renders
> three input fields using array notation in this situation; that way you
> can have error messages that apply to the entity, and it looks logically
> like a single element in the form; getValue() could even return the
> composite date.
>
>> As another example, maybe 2 fields detailing colour and size of
>> clothes, individually the fields may contain valid data, however it is
>> the combinations that need to be able to generate out of stock
>> messages.
>
> Again, this is a good example for a composite element. I'm thinking I
> may need to write a tutorial on this approach...
I thought about this option, but I didnt have a clue how to implement
it as it covered both element rendering and the 'model' side. I must
admit you've kind of lost me with the array notation comment - a
tutorial would be great to see :-)
>> Incidently, is there a convenience method to reset a form once it's
>> been populated?
>
> No! We should have one, though. Could you put an issue in the tracker
> for this?
Will do.
Cheers,
Steve
