Well, in general, the framework doesn't protect much against bad inputs. Setting TextArea's width to 0 could be considered that, but we usually try to let width and height be 0 because effects often cause that to happen. So, it might be worth fixing, maybe just by detecting 0 and not doing anything.
-Alex On 2/12/14 5:21 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: >Hi, > >Managed to reproduce a TLF timeout simply. This may be an edge case but I >can think of a few case where you have small text fields and could run >into this. > > ><?xml version="1.0" encoding="utf-8"?> ><s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"; > xmlns:s="library://ns.adobe.com/flex/spark" > xmlns:mx="library://ns.adobe.com/flex/mx"> > > <!-- Slowly slde down to zero to reproduce bug - can happen when about 2 >or 3 characters wide --> > <mx:Slider id="vslider" minimum="0" maximum="100" value="100" /> > <s:TextArea width="{vslider.value}" text="Apache Flex TLF bug"/> ></s:Application> > > >While trying to fix In looking I just came across this in >StandardFlowComposer. >private function updateCompositionShapes():void > { > for each (var controller:ContainerController in > controller) > controller.updateCompositionShapes(); > } > >Should that be "in _controllerLists"? No idea what a for each (var a in >a) would even do. > >Thanks, >Justin > >
