Re: Completely baffled by NSTabViewController + Autolayout

2015-08-17 Thread Michael David Crawford
> I am missing something big, because I am having nothing but insane trouble > when trying to get a simple tab view working with autolayout. Every path I > head down > has strange problems. I've tried slimming it down to the smallest test > project and > I'm still confused. That's because you're

Completely baffled by NSTabViewController + Autolayout

2015-08-17 Thread Seth Willits
I am missing something big, because I am having nothing but insane trouble when trying to get a simple tab view working with autolayout. Every path I head down has strange problems. I've tried slimming it down to the smallest test project and I'm still confused. The problems I'm seeing are rand

variadic functions missing in bridgesupport file

2015-08-17 Thread Lee Henson
Hi I'm trying to use gen_bridge_metadata to create a bridgesupport file for a c library that contains a mixture of variadic and non-variadic functions. The non-variadic functions appear in the bridgesupport xml, but the variadic functions do not. Is this a known limitation? It looks to me like gen

Re: Constraints across sibling stack views?

2015-08-17 Thread David Duncan
> On Aug 9, 2015, at 10:14 PM, Seth Willits wrote: > > > In my OS X view, I have four popup buttons vertically stacked, each with a > label on the left. The labels all have equal width as each other and are > right-aligned, and the popups all have equal width as well. > > To manage this layo

Re: Nullability annotation "best practice"

2015-08-17 Thread David Duncan
> On Aug 8, 2015, at 1:15 PM, Seth Willits wrote: > > Let's stipulate that _Nullable and _Nonnull are great to have because they > can catch bugs and express API intent better than before, so we want them. > The question is where to put them? > > > _Nullable and _Nonnull make perfect sense t

Re: Referring to self in property initializer

2015-08-17 Thread Fritz Anderson
On 14 Aug 2015, at 8:47 PM, Rick Mann wrote: > > So, adding lazy lets it work with the closure (makes self available to the > closure): > > lazy varbackgroundSession : NSURLSession= > { ... > > I really wish you could do lazy let foo = I don't see why the l

Re: Help understanding Apple's approach in documentation a little better.

2015-08-17 Thread Steve Christensen
On Aug 16, 2015, at 2:58 PM, Alex Zavatone wrote: > Would be REALLY nice if there was something visual that simply communicated > to you that they are not for public consumption. > > If I see it in the left pane of the debugger, and no visual indicators are > stating that it's restricted, It's