Darkstone, I like that you can do everything now with the current scroller but that requires you to know what to do. The advantage of this is that you only have to set a property on the scroller to get the benefits. If it is able to be turned off then it can be added to the class without breaking anything and people can start using it in their applications. Then you don't have to use it but if you want to you can set the cacheViewport property where it makes sense. +1
On Sat, Apr 18, 2015 at 10:03 AM, after24 <vinc...@after24.net> wrote: > DarkStone,Here is a Twitter link to the screen capture : > https://twitter.com/after24_studio/status/589389289059942400 > <https://twitter.com/after24_studio/status/589389289059942400> 1 ->Both > tests are made under gpu render mode.2 ->The difference between the two > techniques is significant, on a nexus 7 : - 25/30 fps with > cacheAsBitmap > - 60 fps with the blitting approch (and a frame budget around 8-10 ms) > > > > -- > View this message in context: > http://apache-flex-development.2333347.n4.nabble.com/Flex-Scroller-optimization-tp46074p46084.html > Sent from the Apache Flex Development mailing list archive at Nabble.com. >
