nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

AGSCallout.customView tap events not working with 100.5

mh10

We have callouts with a customView that has buttons, they are no longer receiving tap events using sdk 100.5. I can see the events in AGSMapView.identifyGraphicsOverlaysAtScreenPoint but they are skipping my view.

Does anyone know of way to get them to function again?

Find more posts tagged with

Accepted answers

Nicholas-Furness

There was a change made at 100.5 requiring that the custom view provide an intrinsic content size, or have enough constraints to size itself (see the release notes😞

A callout with a custom view now uses AutoLayout to size itself to fit that view. A custom view will need to either provide an intrinsic content size or have enough constraints to define it's size. Previously the size of the view's frame was used to size the callout. For views without an intrinsic content size, that same behavior can still be achieved by adding width and height constraints to the view.

I wonder if that's what's happening here?

All comments

Nicholas-Furness

There was a change made at 100.5 requiring that the custom view provide an intrinsic content size, or have enough constraints to size itself (see the release notes😞

A callout with a custom view now uses AutoLayout to size itself to fit that view. A custom view will need to either provide an intrinsic content size or have enough constraints to define it's size. Previously the size of the view's frame was used to size the callout. For views without an intrinsic content size, that same behavior can still be achieved by adding width and height constraints to the view.

I wonder if that's what's happening here?

mh10

It's something related to this I think, I had to fix the view to get them to appear correctly. Everything displays correctly now but can't figure out where the events are going. Its like the parent callout's view is on top of the custom view and is intercepting them?

Nicholas-Furness

Hmm. I'll try to reproduce this later today. If you have a simple repro case to share, please DM me.

Nicholas-Furness

Hi. Having tested a bit, I think that must be it. Make sure that your custom view either can unambiguously determine its width and height from constraints, or set a top-level width constraint and height constraint.

See the attached project. It's a simple custom view with a button and some constraints.

If I remove constraints so that the containing view can't size itself properly, then I still see the button but it doesn't capture taps.

TestCalloutCustomView.zip

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.