Have you tried putting a width on the FormItem itself?

 


From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of jgserrault
Sent: Thursday, June 09, 2005 2:43 AM
To: [email protected]
Subject: [flexcoders] Odd FormItem Behavior

 

Question #1: Is it considered a departure from best-practices to
design and/or use data input forms with input fields side-by-side,
i.e. use FormItem with direction="horizontal"?  I have to say that I
do not recall encountering its use very often, and I seem to be
catching potential Flex bugs when I use it.  Hence my next question...

Question #2:

The following code is the entire section of the mxml file...in case
my problem is one of inheritence. 

<mx:Box direction="vertical" width="450" height="100%">
<mx:Panel id="AddressEntry" title="Sales Inquiry Entry Screen"
     height="100%" width="100%" vScrollPolicy="off">
  <mx:Form width="100%" height="100%">
   <mx:FormItem label="Zip / Street Address" direction="horizontal">
     <mx:TextInput id="Zip" width="60" height="19"/>
     <mx:TextInput id="Street" width="200" height="19"
        focusOut="CheckSubmit()"/>
   </mx:FormItem>
   <mx:FormItem label="Name">
     <mx:TextInput id="Name" width="262" height="19"/>
   </mx:FormItem>
   <mx:Spacer height="10"/>
   <mx:FormItem label="Address Information">
     <mx:TextArea id="AddressBox" text="  " width="262" height="100"
        editable="false"/>
   </mx:FormItem>
  </mx:Form>
</mx:Panel>
</mx:Box>

The problem is that no matter how wide I make the box, panel, or
form, the two textinput fields contained in the first FormItem (the
one using direction="horizontal") will 1) not be placed/rendered on
the same line, and 2) the width of both textinput fields are
seemingly ignored and are both set to some system computed width,
*IF* the sum of each TextInput width field + ((# of fields - 1) *
FormItem.horizontal-gap) exceeds 250. I tested and confirmed this
formula holds true for 2, 3, & 4 textinput fields, and assume it
would for 5+.  I realize I can workaround the unexpected behavior by
surrounding all the TextInput items with HBox, but all the
optimization documentation stresses that over use of containers is
not desirable, and obviously would/should not be necessary if
FormItem functioned as expected. 

So, is this behavior expected, or is this indeed a bug?






Yahoo! Groups Links

Reply via email to