I noticed what appears to be an undocumented behavioral change in 10.2 . Previously, the touch-responsive area of a drawn feature was the feature's geometry. So, a rectangular polygon symbolized with a solid outline and clear fill would register a touch for any tap within the polygon. In 10.2, the touch-responsive area of a drawn feature is any non-transparent symbolization for the feature. So, the same rectangular polygon symbolized with a solid outline and clear fill will *only* register touches on the edge of the polygon, where the alpha is > 0 . The SDK treats any alpha value that it can discern as greater than 0 as touchable, so touchable clear polygons are accomplished by setting the clear fill to an alpha value like .01 / 1%, which will show as clear on the map but still intercept touches.
One of my current projects is an interior mapping app that provides queryable floor maps by showing transparent polygons on top of a tiled map service. The polygons represent rooms and other interior features the user will want to activate/tap, and the underlying tiled map service provides the scale-appropriate, custom cartography that makes the interior map aesthetic and useful.
I'm noting this because I could not find this behavioral change mentioned in the changlelog or the current documentation and because this impacted the use case I outlined above.
