Note also that for the framework, a "visible view" is simply a view that intersects with the clipping rectangle. The clipping rectangle is based on the dirty region used by the last series of invalidate calls. This means that if a view is redrawn, an invalidate with a dirty rectangle intersecting that view was issued (directly or indirectly) by the app.
On Tue, Jun 7, 2011 at 2:12 AM, Romain Guy <[email protected]> wrote: >> Maybe the last sentence should be "That's just not how the UI toolkit is >> supposed to work"? > > You made a simple assumption based on your application. There is > nothing in the UI toolkit that does what you describe. There is not > even a notion of "not enough time to redraw some views." The only > thing the toolkit does is coalesce successive invalidate calls into a > single one by doing the union of the dirty rectangles. What you need > to do is profile your application and figure out why you get so many > invalidate() calls. It seems like your app is somehow causing one of > the top-most views (which usually fill the window) to invalidate. > Don't assume random behaviors from the framework's part without > understanding what your app is doing first. > -- Romain Guy Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them -- 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
