I have a mapview in RelativeLayout defined in main.xml, that also includes another layout as a viewstub to display status message to the users. I set the visibility of the status bar to 'gone' when I inflate the stub. Thereafter any new message (put on the status bar by a thread/async task) will set the visibility to 'visible' to display the message. After the task is done, it remove the message from status bar and set its visibility to gone. BTW GPS is on to get new lat/lng and to move the map accordingly and display overlays
Everything is working...but Question: There are way to many onDraw into mapview even when the device is not moving. I traced it to status bar, anytime new a message is put on status bar, the postInvalidate from there trickles down into mapview, even though the device has not moved a millimeter, lat/lng have not changed, no new map tiles are needed etc. If I remove the status bar, I see normal invalidates to mapview i.e. 2-3 depending on my logic in overlay class which I'm OK with. However when I say large postInvalidates while device is sitting on its behind, they number around 70-80 Any ideas as to whats going on in/with the view hierarchy, how to prevent it ? Is this bug? -- 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
