On Sep 1, 2017, at 6:44 AM, Dave <dave@...> wrote:

Hi,

I’m trying to find some docs on isFlipped. When I search for it in the XCode docs, it only brings up a reference in NSImage and that’s deprecated.

I’m overriding this on some Classes on the Mac, but they are common to iOS and I’m wondering if returning YES, will flip the iOS coordinate system making it bottom left?

Thanks in advance for the help.

Cheers
Dave

On 1 Sep 2017, at 01:11, Quincey Morris <quinceymorris@...> wrote:

On Aug 31, 2017, at 14:07 , Steve Christensen <punster@...> wrote:

Regarding NSPoint, I see it defined as

typedef CGPoint NSPoint;

so its x and y fields will be CGFloats.

Opening up a macOS project and looking at the definition of NSPoint, I see:

#if __LP64__ || TARGET_OS_EMBEDDED || TARGET_OS_IPHONE || TARGET_OS_WIN32 || NS_BUILD_32_LIKE_64

typedef CGPoint NSPoint;

…

#else

typedef struct _NSPoint {
    CGFloat x;
    CGFloat y;
} NSPoint;

…

#endif

So, it was the same size as CGPoint, but a different struct name, which was enough to create an ABI incompatibility. You could opt into the new typedef for 32-bit by using NS_BUILD_32_LIKE_64.

On Aug 31, 2017, at 12:39 PM, Quincey Morris <quinceymorris@...> wrote:

On Aug 31, 2017, at 12:19 , Jens Alfke <jens@...> wrote:

I don't see how they could be incompatible if they're the same size.

I don’t remember the exact details either, but one issue is that there are places in the Obj-C runtime/metadata/whatever where the @encode string of a method signature matters, and some similar same-size, same-representation types are represented by different letters in the string. This could mean that although method parameters and return values were bit-for-bit identical, the type encoding made the methods incompatible.

One particular example I remember, unrelated to this thread’s topic, is that in 64-bit, NSUInteger encoded to “Q” (quad-word, i.e. long long) not “L” (long). Both types were 8 bytes, and NSUInteger was even typedef’ed to long (IIRC), but “L” was never used in that architecture.

The NSPoint/CGPoint thing was something like that. IIRC, NSPoint used float, and CGPoint used CGFloat, and those @encoded differently for some reason.

On 31 Aug 2017, at 13:05, Alex Zavatone <zav@...> wrote:

Look at the types that back them.

Structs and CGFloats?

On Aug 31, 2017, at 6:03 AM, Dave <dave@...> wrote:

Hi,

Is there any real difference between NSPoint, NSRect, NSSize etc. and the CG versions?

I can use the CG Versions on Mac and iOS but the NS versions only on Mac.

If I only used the CG versions it would compile ok for both platforms, but is this wise, or is it best to use NS on Mac?

All the Best
Dave

On Aug 31, 2017, at 6:03 AM, Dave <dave@...> wrote:

Hi,

Is there any real difference between NSPoint, NSRect, NSSize etc. and the CG versions?

I can use the CG Versions on Mac and iOS but the NS versions only on Mac.

If I only used the CG versions it would compile ok for both platforms, but is this wise, or is it best to use NS on Mac?

All the Best
Dave

On Aug 30, 2017, at 2:09 PM, Alex Zavatone <zav@...> wrote:

On Aug 30, 2017, at 3:54 PM, Ben Kennedy <ben@...> wrote:

On 30 Aug 2017, at 1:37 pm, Alex Zavatone <zav@...> wrote:

In iOS, when I’m making an Objective-C singleton, in the public method that returns the instanceType, we need to put the class name.  Is there a way to do this dynamically instead of entering the class name all the time?  

Why is this necessary? Apologies if I'm missing something obvious, but what's wrong with literally using DataSingleton (in your example)?

Even if the method is called on a subclass it should still work as desired because you're calling [self alloc], not [DataSingleton alloc].

-ben

I’m able to turn the sharedInstance method from being dependent on my changing the class name and being this:

@implementation CrewActionsDataSingleton

+ (instancetype)sharedInstance

{

    static TheClassName *instance;

    static dispatch_once_t onceToken;

    

    dispatch_once(&onceToken, ^{

        instance = [[self alloc] init];

    });

    return instance;

}

 To this:

@implementation CrewActionsDataSingleton

+ (instancetype)sharedInstance

{

    static id instance; 

    static dispatch_once_t onceToken;

    

    dispatch_once(&onceToken, ^{

        [self new];

    });

    return instance;

}

I’m able to turn the sharedInstance method from being dependent on my changing the class name and being this: Good point on making a snippet.  I think I change computers too often though. It’s another thing to manage.

Thanks for the tips.  Best brain trust ever.

Alex Zavatone