So, all the bad things in the title aside, I have a MapView
(and several other views) inside ScrollView
(I know, and I advised a thousand times against placing MapView in the scroll container, but this is what the client wants), and when I I scroll ScrollView
up, MapView
finishes drawing over the ActionBar
. I set zOrderOnTop
to true on GoogleMapOptions
, which I pass to the MapView
constructor, which prevents this when I first add the MapView
to the view hierarchy, but when I move and return to the application it is again drawn over the ActionBar.
I need to artificially name MapView lifecycle events when a MapView is created and placed in a ScrollView, because I am making a network call, and depending on the data that I can or cannot add the map.
I searched on Google and SO for ways to mitigate this, and I didn't come up with anything. The phones I'm testing on are Android 4.1+, so it should use a TextureView
implementation, not a SurfaceView
implementation of MapView.
source share