I think the solution to this would be to override FormItem class.
Have a look at the source code of FormItem in FlexSDK/frameworks/source
There is a class FormItemLabel which is used to render the label but
for some reason
it has been kept private.
See if you can override the commitProperties method and write your
own createItemLabel method.
On May 21, 2007, at 7:55 PM, borekbe wrote:
Yeah, I figured that out although even this is not completely perfect
(for example, visual designer in Flex Builder doesn't support
containers inside mx:Form very well). What about the second problem -
more complicated labels, e.g. labels containing graphics? Can this be
solved? I didn't find any work around so far...
--- In [email protected], "Flexing..." <[EMAIL PROTECTED]> wrote:
>
> The form is not one columed..
> You can place multiple form items in a container like HBox, VBox
etc.
> e.g.
> <mx:Form>
> <mx:HBox>
> <mx:FormItem label="item1">
> <mx:VBox>
> <mx:RadioButton/>
> <mx:RadioButton/>
> </mx:VBox>
> </mx:FormItem>
> <mx:FormItem label="item2">
> <mx:Checkbox/>
> </mx:FormItem>
> </mx:HBox>
> </mx:Form>
>
> On May 21, 2007, at 2:07 PM, borekbe wrote:
>
> > Hi, I'm new to Flex and wanted to ask a beginner's question -
what are
> > the pros and cons of using mx:Form versus the set of input fields,
> > labels etc.?
> >
> > I like the required=true functionality but on the other hand,
layout
> > possibilities are somehow limited (the form is always one
column only,
> > what if I want more complicated labels? etc)
> >
> > I would be grateful for any comments on this topic.
> >
> > Thanks,
> > Borek
> >
> >
> >
>
