I found a workaround at this url - http://stackoverflow.com/questions/4080347/adding-radio-button-dynamically-twice-error-2025-the-supplied-displayobject
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 HBox 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 fly. 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 code. -- View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Any-workaround-for-this-bug-tp5256p5341.html Sent from the Apache Flex Users mailing list archive at Nabble.com.
