# Map Layout Update

DevFeed: [Map Layout Update](<https://devfeed.tech/articles/map-layout-update-19360.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/map-layout-update/>)

Author: Shai Almog

Published: 2018-03-07T00:00:00Z

Content type: tutorial

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [API](<https://devfeed.tech/topics/api.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [blog-post](<https://devfeed.tech/tags/blog-post.md>), [class](<https://devfeed.tech/tags/class.md>), [components](<https://devfeed.tech/tags/components.md>), [native](<https://devfeed.tech/tags/native.md>), [os](<https://devfeed.tech/tags/os.md>), [update](<https://devfeed.tech/tags/update.md>)

## AI overview

This blog post describes an update to the Codename One MapLayout class. The update addresses scaling problems by using asynchronous, batched data fetching and adds alignment support for positioning components on a map.

## Source excerpt

__ The information in this blog post is slightly out of date. Check out the newer blog post that covers positioning components on the map. A while back I introduced a MapLayout class as a tip and discussed the usage of this class. Since that introduction we ran into some scale issues as the layout misbehaved when a lot of elements were added to it. The crux of the issue is in the native map API which runs on the OS native thread and the Codename One API which needs immediate responses for layout.