The code in setScrollXY is not called anywhere in the class, and was old test code to get around the fact that some fields/methods are not available in sub-classes in different packages.
It can be and should have been removed, but then again, who has time for that? Michael On Mar 12, 1:44 pm, Romain Guy <[email protected]> wrote: > Do NOT use this implementation. The setScrollXY() method changes field > by reflection. Not only is it likely to break it's also VERY VERY > inefficient. Especially given the lookup is done *every* single time. > View already has methods to change the scroll X/Y values. > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
