Databases
StackOverflow2013
Postsdbo
POPerformance of multiple MapFragments (Android Map API v2)
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPerformance of multiple MapFragments (Android Map API v2)
    primarykey
    data
    text
    <p>I searched the docs of the new <a href="https://developers.google.com/maps/documentation/android/" rel="nofollow noreferrer">Google Android Map API v2</a>, but didn't find anything about it. Before v2 we (officially) couldn't properly display more than one map per application (process). I assume that with <code>MapFragment</code> implementation it's no longer an issue. I also know, that <code>Fragments</code> can be self-contained since API 17. And, last but not least, there is compatibility package, which makes it possible to port it all back to at least API 8 (in API 7, there's no OpenGL 2.0 so the maps wouldn't work afaik).</p> <p>Sa I have all the ingredients to port my app to Maps API v2 and implement the following scenario: <code>ViewPager</code> contains <code>Fragments</code> and each of them contains a <code>MapFragment</code>.</p> <p>But should I do it? I mean, <strong>would I face performance issues</strong> if I had e.g. 20 <code>Fragments</code> containing <code>MapFragments</code> in a <code>ViewPager</code>?</p> <p>If you found anything that addresses my concern in the docs or somewhere else, please tell me.</p> <hr> <p><strong>EDIT: Example usage</strong>: Let's imagine a screen containing informations about some specific item - place, event, article. Also let's imagine that, among other informations, it must contain a map to be fully functional. But I would like the user to be able to swipe to another item if he wants. Each item has its own map.</p> <p>Side note: I know that I can implement one map outside the <code>ViewPager</code> and just update it based on the currently displayed item, but it's not what I'm looking for - it's not user-centered design.</p> <hr> <p><strong>Possible solution</strong> (but not checked yet). <code>ViewPager</code> only keeps a few (default - 3) Fragments in it's cache and recreates them when they're about to show up, so there won't be much memory overhead as only a few <code>MapFragments</code> are needed. The performance problem may be the <code>MapFragment</code> inflation which is quite heavy, I believe - but that can be solved with recycling of <code>MapFragments</code>. </p> <hr> <p>So why won't I implement it if I believe it will work nice? There's another problem which makes it impossible to move <code>MapFragments</code> without the app look like it's broken. <a href="https://stackoverflow.com/questions/14419521/moving-mapfragment-surfaceview-causes-black-background-flickering">See this</a>.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USMichał K
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POPerformance of multiple MapFragments (Android Map API v2)
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POPerformance of multiple MapFragments (Android Map API v2)
      1. USuser291701
      1. VTFavorite
    3. VO
      singulars
      1. POPerformance of multiple MapFragments (Android Map API v2)
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHave you made any tests?
      singulars
      1. POPerformance of multiple MapFragments (Android Map API v2)
      1. USMarek Sebera
    2. CONo, because this API is flawed in so many ways, it's not worth it to implement in many cases (my included)
      singulars
      1. POPerformance of multiple MapFragments (Android Map API v2)
      1. USMichał K
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload