# \[Solved\] How do the event blocks for the Map component work?

**URL:** https://community.thunkable.com/t/solved-how-do-the-event-blocks-for-the-map-component-work/73742
**Category:** Questions about Thunkable X
**Tags:** solved
**Created:** [March 30, 2019, 9:39am UTC](https://community.thunkable.com/t/solved-how-do-the-event-blocks-for-the-map-component-work/73742 "2019-03-30T09:39:57Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![Mark](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/mark/32/18133_2.png) [@Mark](https://community.thunkable.com/u/Mark)
#### Post date: [May 1, 2019, 6:57pm UTC](https://community.thunkable.com/t/solved-how-do-the-event-blocks-for-the-map-component-work/73742/3 "2019-05-01T18:57:47Z")

</div>

Those blocks are triggered, respectively, when a user clicks on a map, long presses on a map (i.e. clicks and holds their finger down) or clicks on the the “bubble” that appears when they click on a marker.

Unfortunately, there are a few known issues with the Map event blocks. One is that the onCalloutPress doesn’t appear to work at all. Another is that the output blocks for the events (e.g., `"coordinate", "position" and "event"`) are either incorrectly named, unhelpfully named or simply unusable.

I’ve created a sample project that you can use that shows how, despite the issues mentioned above, to get latitude and longitude for the onPress, onLongPress, onMarkerPress blocks: [Thunkable](https://x.thunkable.com/copy/91f287542b31aa70b14d50c1229f40b6)

If you just want to see the blocks, here’s a screenshot:

 ![53%20AM](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/0/f/0f4258ff7aaf77d21cf18f7c832f32b02da78729.png)

I hope this helps.

-Mark

---

_[View the full topic](https://community.thunkable.com/t/solved-how-do-the-event-blocks-for-the-map-component-work/73742)._