• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Interface Builder "layout" versus "frame"
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Interface Builder "layout" versus "frame"


  • Subject: Re: Interface Builder "layout" versus "frame"
  • From: John Stiles <email@hidden>
  • Date: Thu, 8 Nov 2007 11:06:38 -0800

I checked out some Carbon APIs but it looks like Carbon tab views don't have the same beefy margins as NSTabViews, so even if I could find an appropriate constant, the values would not match up.

Bummer. I guess it's hard-coding for me :(

On Nov 8, 2007, at 10:44 AM, John Stiles wrote:

That's a shame; I don't want to require 10.5 just yet.
So basically I should just look at what IB uses for layout values and hard-code? Or maybe would it be possible to leverage HITheme or some other Carbon API?



On Nov 8, 2007, at 10:34 AM, Joe Ranieri wrote:


On Nov 8, 2007, at 13:26, John Stiles wrote:

I've noticed that Interface Builder shows not only a "frame" value for object sizes, but also a "layout" value.

I am trying to create a few controls programatically and it seems like I'd get results a lot closer to what I'm expecting if I could create them with a "layout" rectangle instead of a "frame" rectangle. For instance, if I make an NSTabView, it's significantly inset compared to the NSRect I've set. But if I go into IB and create a tab control and set up its "layout" rectangle to match what I want, the positioning is perfect.

So programatically, how do I work with "layout" rectangles instead of "frames"?

http://developer.apple.com/documentation/DeveloperTools/Reference/ NSViewIBAdditions_Reference/Reference/Reference.html perhaps?



I know that technically I could just hard-code the margin sizes of controls but I am hoping to avoid this… it doesn't seem future- proof.


This was the only route prior to 10.5, sadly.

Joe Ranieri
Lead Magician, Alacatia Labs, Inc.
http://alacatia.com

_______________________________________________

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:
40blizzard.com


This email sent to email@hidden

_______________________________________________

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:
40blizzard.com


This email sent to email@hidden

_______________________________________________

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


References: 
 >Interface Builder "layout" versus "frame" (From: John Stiles <email@hidden>)
 >Re: Interface Builder "layout" versus "frame" (From: Joe Ranieri <email@hidden>)
 >Re: Interface Builder "layout" versus "frame" (From: John Stiles <email@hidden>)

  • Prev by Date: Re: Interface Builder "layout" versus "frame"
  • Next by Date: Re: Interface Builder "layout" versus "frame"
  • Previous by thread: Re: Interface Builder "layout" versus "frame"
  • Next by thread: Re: Interface Builder "layout" versus "frame"
  • Index(es):
    • Date
    • Thread