On Dec 25, 2010, at 12:27 PM, Matt Neuburg wrote: > > On Dec 25, 2010, at 9:52 AM, Alex Kac wrote: > >>> Again - "the popover"? You never said anything up to this point about a >>> popover, so how does it come in? >> >> Fromt the UISearchDisplayController. It presents the popover for us in this >> case which I'm not too crazy about as I'd like more control over that, but >> it is what it is. > > Okay, but I'm none the wiser. This is not something endemic to a > UISearchDisplayController, so *you* must be presenting the popover. So the > question would be how you're doing that.
No....we're not. The popover comes up automatically when you type into the UISearchBar as provided by the display controller. I can go into IB (our project does not have this done in IB, btw) add a UISearchBar with a UISearchDisplayController and have zero code and when you tap in the search bar the controller brings up its own popover. In fact I just took a simple iPad template project with a UISplitViewController. Opened its DetailView.xib and added a UISearchDisplayController. Removed its datasource and delegate connections just so I could make this an example. Built and ran the project and voila - you get an automatic popover. So I am *not* presenting any popover, UISearchDisplayController is, as its standard behavior. > >> That sparked me looking into how we instantiate the controller and then I >> realized the mistake. > > And this is precisely the sort of thing I was prompting for. All of this > information (how the controller is instantiated, how the popover came into > being) was absent from the original question. It's good that you were able to > solve your problem, but if all the relevant information is kept secret, > that's the *only* way your problem is going to be solved; the question > equates to an empty exercise. m. Right, but at the time I had not even thought about that part. I was simply thinking about how that specific controller works and was attacking it from the side of what I needed to do in its subclass. It was the process of writing the problem out that made me think through it. I had thought that perhaps someone in the list had seen a similar issue (I saw mention of it on the Dev Forums, but it didn't have any real info) which is the only reason I posted here._______________________________________________ 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
