Re: A bug with NSWindow's convertBaseToScreen: method ?
Re: A bug with NSWindow's convertBaseToScreen: method ?
- Subject: Re: A bug with NSWindow's convertBaseToScreen: method ?
- From: Ricky Sharp <email@hidden>
- Date: Wed, 18 Apr 2007 04:03:03 -0700
On Wednesday, April 18, 2007, at 04:51AM, "Mike Zornek" <email@hidden> wrote:
>In working on the results of my previous message/issue[1] and I believe I've
>run into a bug with NSWindow's `convertBaseToScreen:` method. Or maybe just
>a misunderstanding on my part.
>
>> This Xcode project demos what I think is a bug with NSWindow's
>> `convertBaseToScreen:` method. Basically when I pass it an origin from a
>> button that lives within an NSBox the resulting point isn't the true screen
>> origin.
>>
>> The app demos this by having two buttons, one in the window and one in a
>> NSBox. When you click on the button it will position a Dummy window directly
>> bellow the button. This works great for Button One, but for Button Two (which
>> lives in the NSBox) the Dummy Window's position is off.
Not a bug. I do a very similar thing with the positioning of custom help tags (which use overlay windows). I don't have the code in front of me, but I believe I used convertPoint:toView: (where the view param is set to nil) before calling convertBaseToScreen.
I think I then sprinkled in one or two more lines to make it resolution-independent savvy. Start with the above though and if you're still having issues, I'll look at my code this afternoon.
--
Rick Sharp
Instant Interactive(tm)
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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