I am correct that it is currently not possible to submit a 64-bit-only build to
the App Store?
Kind of a Catch-22; I have no 32-bit devices here anymore, and the simulator in
current Xcode doesn't offer them. I guess I need to build a 32-bit-only
version, test it, then switch back to fat 32&64?
On Aug 4, 2015, at 8:37 AM, Scott Ribe wrote:
>
> I am correct that it is currently not possible to submit a 64-bit-only build
> to the App Store?
>
> Kind of a Catch-22; I have no 32-bit devices here anymore, and the simulator
> in current Xcode doesn't offer them. I guess I need to build a 3
On 03 Aug 2015, at 06:01, Graham Cox wrote:
> Thinking further, I do have a NSTabView between the window and these fields,
> and the tab on which the fields are placed are not on the default tab. I seem
> to recall there were issues with tab views a long time ago, and perhaps it’s
> naive to as
I was hoping to use a protocol to define the objects I could put into an
NSOutlineView. Unfortunately, NSOutlineView has datasource methods that return
AnyObject, and I can't seem to return a variable of my protocol type as an
AnyObject.
I'm curious why, and what the right approach might be? If
On Aug 4, 2015, at 15:58 , Rick Mann wrote:
>
> I'm curious why, and what the right approach might be?
As to why, the problem is that instances of a type conforming to a protocol
aren’t necessarily objects. If you want them to be, try declaring your protocol
like this:
protocol P: cla
> On Aug 4, 2015, at 16:22 , Quincey Morris
> wrote:
>
> On Aug 4, 2015, at 15:58 , Rick Mann wrote:
>>
>> I'm curious why, and what the right approach might be?
>
> As to why, the problem is that instances of a type conforming to a protocol
> aren’t necessarily objects. If you want them to
