On 6 Mar 2015, at 4:25 pm, Ken Thomases <[email protected]> wrote:
>> So you're saying it's a bug? > > I think the bug is that IB hides the existence of the sub-NIB. If IB > presented the sub-NIB with all of the usual placeholders and put a Shared > User Defaults Controller into it when you set a binding on it, etc., that > would help make this clear. > > Also, it's a bug that IB will blithely let you create connections from > objects in the sub-NIB to objects outside the sub-NIB when those connections > won't survive to runtime. That's what I was getting at, I guess. There's no indication that one is doing anything wrong (other than failure to work, of course). > >> It also seems that the row height is based on its height. > > How so? To my knowledge, Cocoa doesn't yet support determining row height > automatically based on the height of cell views (presumably determined by > auto layout). UIKit has that, but AppKit does not. And it's not clear to me > if it makes sense for a table that can have multiple columns, since each > column's cell view can be different. > > You set the table view's row height on the table view itself, on the Size > inspector. There is an Automatic mode, but that uses the row size style from > System Preferences. I had it set to automatic mode, and the unused table cell view was set to X points high. Each time I changed its height and ran it again, the height of the rows changed accordingly. No big deal because I needed to implement the delegate method anyway, but I was surprised. -- Shane Stanley <[email protected]> <www.macosxautomation.com/applescript/apps/> _______________________________________________ Cocoa-dev mailing list ([email protected]) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
