Well both are possible if you only consider the scope of the v4 compatibility library. Since the implementation of the former solution would change the classes of Fragment, FragmentManager, and FragmentPagerAdapter in that library, the changes would not affect someone using their own native FragmentPagerAdapter implementation (or possibly the one in the v13 compat lib).
I have updated the bug linked with a .zip showing the errant stock behavior, a "Fix #1" of the FragmentManager method, and a "Fix #2" of the OnPageChangeListener method. The .zip also has a readme detailing an easy way to see the changes made for each fix. I've decided to go with Fix #2 for ActionBarSherlock for the sake not introducing future headaches and inconsistencies with both the SDK and future revisions of the v4 compatibility library. I can only hope that someone responsible for ViewPager sees this, agrees, and adds the additional callback (or something equivalent) to the next revision of the library to allow for this fix to utilized by everyone. -- 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
