flex-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: Any workaround for this bug?
Date Sat, 08 Mar 2014 00:15:18 GMT
One option may be to not use RadioButton at all.  Use a checkbox with a
radio button icon, and manage the selection yourself.  Then there is no
RadioButtonGroup which might be what is causing the problem.

On 3/7/14 1:57 PM, "akm" <arun.flexer@gmail.com> wrote:

>I found a workaround at this url -
>It has temporarily solved the problem, but not fully.
>We have an ugly design code which worked in the past with sdk 3.4 but is
>haunting us with flex 4.11 migration. we have code to construct nested
>containers holding data (labels, radio buttons etc. in tabular format with
>various rows and columns, labels/radiobuttons/etc are nested inside each
>hbox as child). The code does dynamically add and remove components on the
>The performance is hit very badly. We do have an alternate efficient
>solution implemented with datagrid and item renderers in another place. We
>are compiling the code with Flex 3 compatibility on.
>When compiled changing from mx:radiobutton, mx:radiobuttongroup to
>s:RadioButton, s:RadioButtonGroup and removing Flex3 compatibility option,
>we are seeing it slow but atleast renders fine.
>we have few options:
>(A) rewrite everything using renderes
>(B) get out of flex3 compabitility mode. (but we have another issue with a
>custom component text placement which is not calculating the actual text
>width correctly).
>I wish i could explain the problem better with a sample, i have a huge
>View this message in context:
>Sent from the Apache Flex Users mailing list archive at Nabble.com.

View raw message