Closed incanus closed 11 years ago
I'm seeing weird behavior in our SDK reported by a user, so I tested it with your release and see the same effect.
release
Essentially, when a map view is inset from its superview, clipping of shape paths happens at that map edge.
For example, with this code:
https://gist.github.com/62053add1138f9ba03d9
The map view is inset from the main view by 220 pixels on the top. When the shape approaches the top via map panning, it gets clipped erratically.
This does not seem to happen when the map view is the full size of the containing view.
The user also reports that it happens around 150 or more pixels, which of course draws me to this line:
https://github.com/Alpstein/route-me/blob/release/MapView/Map/RMShape.m#L191
But changing it doesn't seem to have any affect.
Any ideas here?
Think I might have fixed it above.
Cool, I'll send my fix up to you soon, along with a bunch more of our recent work.
I'm seeing weird behavior in our SDK reported by a user, so I tested it with your
release
and see the same effect.Essentially, when a map view is inset from its superview, clipping of shape paths happens at that map edge.
For example, with this code:
https://gist.github.com/62053add1138f9ba03d9
The map view is inset from the main view by 220 pixels on the top. When the shape approaches the top via map panning, it gets clipped erratically.
This does not seem to happen when the map view is the full size of the containing view.
The user also reports that it happens around 150 or more pixels, which of course draws me to this line:
https://github.com/Alpstein/route-me/blob/release/MapView/Map/RMShape.m#L191
But changing it doesn't seem to have any affect.
Any ideas here?