On 6 Aug 2010, at 00:03, Fritz Anderson wrote: > On 5 Aug 2010, at 2:57 AM, Gerriet M. Denkmann wrote: > >> I have an MKMapView which sometimes does: >> [ mapView addSubview: selectorView ]; >> and selectorView contains a UIPickerView. > > I'm not sure why you feel it necessary to drop your selector view directly > into the map view?
No reason at all. Just a case of old habits - overlapping subviews once used to be forbidden. > My experience is that MKMapView is a sensitive thing. It would not surprise > me if it assumed that its top-level view contained only its own content. > > What happens if wrap the map view and the selector view in a common root view? Well, I replaced: [ mapView addSubview: selectorView ]; with: [ [ mapView superview ] addSubview: selectorView ]; and it seems to be working much better. > If you add the selector view last, it would overlay the map view without > mucking with its internals. > > Root view > Map view > Selector view > Picker Thanks a lot for your help! Gerriet. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com