Re: Semi-Transient NSPopover disappearing when it shouldn't (10.7.3)
Re: Semi-Transient NSPopover disappearing when it shouldn't (10.7.3)
- Subject: Re: Semi-Transient NSPopover disappearing when it shouldn't (10.7.3)
- From: Antonio Nunes <email@hidden>
- Date: Fri, 24 Feb 2012 20:55:10 +0000
On 24 Feb 2012, at 16:55, Corbin Dunn wrote:
>> I have a few popovers that, as far as I'm aware of, were working fine up to 10.7.2. Now, in 10.7.3, when the popover appears, if a user clicks on it, it often disappears, whether the click is on the background or on a UI item. I haven't figured out the trick exactly of the way in which clicking makes the popover go away, but it appears to be sensitive to how you click. A popover should never go away though when it is clicked upon. I think this is a bug in 10.7.3. Various internet searches for this issue did not return any results, nor did searching Apple's developer forums.
>>
>> Any ideas what might be causing this, or how to work around the issue? Has anyone else even encountered this issue?
>
> I don't believe we changed NSPopover in 10.7.3, but it is possible that something else is affecting this.
>
> It sounds like something outside of the popover is becoming the first responder, and that causes the popover to go away.
It was a bit as if there was a prolonged period where the underlying window (or an element of it) was first responder. If we waited long enough before clicking anywhere on the popover, or if we pressed tab to activate another text field in the popover then clicking would function normally.
As I wrote in answer to Seth Willis, I was able to fix the issue (the email still hasn't shown up on the list, so I'll repeat it here):
> On 23 Feb 2012, at 21:52, Seth Willits wrote:
>
>>> I have a few popovers that, as far as I'm aware of, were working fine up to 10.7.2. Now, in 10.7.3, when the popover appears, if a user clicks on it, it often disappears, whether the click is on the background or on a UI item.
>>
>> Can you replicate this in a test project?
>
> I couldn't replicate it in Apple's sample "Popover" project, but since it had a somewhat different implementation than what I had devised, I changed my strategy to one more similar with that of the sample, and, for now, it looks like it fixed the issue.
>
> I had my popovers in separate nibs, which each had a popover and the file's owner was the popover view controller (not the one the IB automatically creates when you drag in a popover, since I needed the file's owner to be the popover controller, so I had deleted the one IB creates).
>
> Now I changed strategy to have one popover in the view controller that controls and displays the popovers, and the nibs have only the popover view controller and the the view. Now the popover is created on the fly in the parent view controller, instead of residing in the nib. This appears to work better in 10.7.3.
-António
--------------------------------------------
I try to take one day at a time, but sometimes, several days attack me all at once!
--------------------------------------------
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden