bladewheels

Well, the prod. code *might* be an example but it's hardly small nor focused on demo'ing the behaviour *occasionally* seen; I might have trouble convincing the suits that this latest version will fix our (sporadic) problem without a demonstrable use case. (So *occasional* that I've never seen it in QA nor Dev but customers have repeatedly reported it in Prod...) Being new to AS, timelines, tweening et. al. I was hoping for a small app that would break/fail on pushing a button with the old lib but not the new. I understand it's a lot to ask, but I thought it would be worth asking - never say never, right? I believe the TweenLite version in use was v11.101 from 10/22/09, 11:50PM according to com/greensock/changelog.txt I only started working at this firm a couple of weeks ago so I guess I am letting you know about this issue ASAP; apparently a displayable item *freezes* but, being so new to it all I can hardly describe the way TL is used here. Thanks for your prompt response and the (apparent) wonderfulness of your contributions.

Any chance of posting a sample app that fails with the old TweenLite but passes with the new version? I'm a Flex n00b & have been tasked with proving that we can re-introduce TweenLite, having removed it due to random freezing in our production code. TIA