Hi darkstone, * /This issue is probably caused by Scroller and the viewport's layout. When scrolling with finger, the Scroller will update viewport's horizontal and vertical scroll positions (actual work is done by viewport.layout), and might involk some other layout API of the viewport. The instance to the viewport.layout property is responsible for updating the viewport's scrollRect, and maintaining the layout of the viewport's direct children, depending on the structure of the viewport's children, this might consume a lot CPU resources./*
I'm not sure about that because when the actual viewport is replaced by it's cached version, the _viewport property of the scroller is actualized to point on the viewportCache. So the horizontal and vertical scroll positions shouldn't affect the actual viewport layout during scroll operations. This stackoverflow <http://stackoverflow.com/questions/10037262/building-small-gui-engine-visible-vs-addchild-removechild> post could be an explanation of the difference in performance. Vincent. -- View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Scroller-optimization-tp41774p41883.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
