32-bit / 64-bit roadmap

So far as I can see, all recent Mac OS systems are 64-bit on 64-bit hardware and can run an app shipped in 64-bit only. And 32-bit continues to run fine. But what about the future? Perhaps we can only speculate about whether 32-bit apps will be deprecated, but maybe Apple have started to hint that

How to save a Dictionary Network to a plist file?

Hi All, I have Network of Dictionaries containing “LTWNodeInfo” Classes. LTWNodeInfo contains a Child Dictionary which in turn contains other LTWNodeInfo. The Key to these dictionaries is a Unique ID string called the NodeID. @interface LTWNodeInfo @property (copy)NSString*

Re: How to save a Dictionary Network to a plist file?

> On Jan 21, 2016, at 9:05 AM, Dave wrote: > > This all works great and now I’d like to save this to a plist file and load > it later on. Does it have to be in plist format? The easiest way to persist this data would be to make LTWNodeInfo implement the NSCoding protocol, then use an NSArchiv

Re: How to save a Dictionary Network to a plist file?

Hi, It doesn’t *have* to be plist, but if it were it would be easier/possible to view/edit it. I need a quick solution to be honest, if its really quick to implement NSCoding then I could do that for how, and revisit it later on. For the plist solution do you know of anything available that wo

Re: 32-bit / 64-bit roadmap

On 21 Jan 2016, at 10:45 AM, Aandi Inston wrote: > > So far as I can see, all recent Mac OS systems are 64-bit on 64-bit > hardware and can run an app shipped in 64-bit only. And 32-bit continues to > run fine. > > But what about the future? Perhaps we can only speculate about whether > 32-bit a

Problem Archiving/Un-archiving Custom Objects

Hi, I’ve got it working using NSCoding for now and I can review to later. I have one crashing problem though, I’m getting a crash when one of the properties in my LTWNodeInfo is dealloc. It’s an NSIndexPath class, the rest seem to be ok. i’m wondering if it is to do with the way in which I’m c

Re: 32-bit / 64-bit roadmap

> On Jan 21, 2016, at 1:32 PM, Fritz Anderson wrote: > > On 21 Jan 2016, at 10:45 AM, Aandi Inston wrote: >> >> So far as I can see, all recent Mac OS systems are 64-bit on 64-bit >> hardware and can run an app shipped in 64-bit only. And 32-bit continues to >> run fine. >> >> But what about

Re: 32-bit / 64-bit roadmap

> On Jan 21, 2016, at 1:57 PM, SevenBits wrote: >> On Jan 21, 2016, at 1:32 PM, Fritz Anderson wrote: >> >> On 21 Jan 2016, at 10:45 AM, Aandi Inston wrote: >>> >>> So far as I can see, all recent Mac OS systems are 64-bit on 64-bit >>> hardware and can run an app shipped in 64-bit only. And 3

Re: Problem Archiving/Un-archiving Custom Objects

No, that’s weird, your code looks ok to me. Have you tried using the static analyzer? Or the address sanitizer? Or running with NSZombies? —Jens ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comm

Re: 32-bit / 64-bit roadmap

> On Jan 21, 2016, at 1:57 PM, SevenBits wrote: > > Unrelated, but… are these the official code names? Yup, the road map got leaked last month. And 10.14 will be Rancho Cucamonga and 10.15 is Manteca*. —Jens * sure to be a big hit in Spanish-speaking countries! __

Re: Faster scrolling after resizing window

That doesn’t make much sense. Try comparing samples before and after. What is different? corbin > Il giorno 17 gen 2016, alle ore 5:16 AM, Martin Huber > ha scritto: > > I have a strange problem in my application (on 10.11, but I don't know > whether that's important). After opening a docume

Re: Problem Archiving/Un-archiving Custom Objects

On Jan 21, 2016, at 13:47 , Dave wrote: > > myObjectCopy. pNodeIndexPath = self. pNodeIndexPath; //Copy > Attribute on Property You have to be careful, depending on what’s already happened. If the object was copied with NSCopyObject, which might have happened in NSObjet’s copy

Re: Problem Archiving/Un-archiving Custom Objects

> On 21 Jan 2016, at 23:04, Quincey Morris > wrote: > > On Jan 21, 2016, at 13:47 , Dave > wrote: >> >> myObjectCopy. pNodeIndexPath = self. pNodeIndexPath; //Copy >> Attribute on Property > > You have to be careful, depending on what’s alread

Re: 32-bit / 64-bit roadmap

> On Jan 21, 2016, at 3:57 PM, SevenBits wrote: > >> On Jan 21, 2016, at 1:32 PM, Fritz Anderson wrote: >> >> On 21 Jan 2016, at 10:45 AM, Aandi Inston wrote: >>> >>> So far as I can see, all recent Mac OS systems are 64-bit on 64-bit >>> hardware and can run an app shipped in 64-bit only. An

Re: Problem Archiving/Un-archiving Custom Objects

On Jan 21, 2016, at 15:22 , Dave wrote: > > I’m relying of the copy attribute for the NSString’s, do I need to change > these to do a [xxx copy] too If you’re writing the setter yourself, you must do the copy yourself. If you’re using the synthesized setter, it’s done for you. In your own

Re: Problem Archiving/Un-archiving Custom Objects

> On 22 Jan 2016, at 10:04 AM, Quincey Morris > wrote: > > In general, like in inits, you will want to assign directly to instance > variables rather than use property setters Same applies to -initWithCoder: If you call a lot of property setters there, performance is slow. It might not matt

Re: How to save a Dictionary Network to a plist file?

I'm surprised nobody has mentioned JSON. You might later look at it. It can help sometimes by showing where a model is over engineered and can be simpler and more flexible and reusable, but it also might not fit. Sent from my iPhone > On Jan 22, 2016, at 2:05 AM, Dave wrote: > > Hi All, >

Re: How to save a Dictionary Network to a plist file?

You can use NSCoding to write the object out to disk and read it back. If you want to convert it to a dictionary, you can save it as a pList I’m spent right now, but if you’re interested I can send you my code for saving and restoring my lists of CLLocations using NSCoding. It will have to wait

Re: How to save a Dictionary Network to a plist file?

> On Jan 21, 2016, at 4:36 PM, dangerwillrobinsondan...@gmail.com wrote: > > I'm surprised nobody has mentioned JSON. > You might later look at it. From the perspective of Dave’s question, JSON is the same thing as a plist except it doesn’t support NSData or NSDate. It’s not going to offer an

Re: 32-bit / 64-bit roadmap

> On Jan 21, 2016, at 5:04 PM, Jens Alfke wrote: > > Yup, the road map got leaked last month. And 10.14 will be Rancho Cucamonga > and 10.15 is Manteca*. and 10.16 Death Valley. -- Bill Cheeseman - wjcheese...@comcast.net ___ Cocoa-dev mailing

Using an anchor in NSURL file url

Colleagues, In OSX I'm using an NSURLRequest to load a file url in WKWebView. Works fine unless I try to add an anchor to the path, for example, [path]/filename.html#anchorname The problem appears to be that the # gets escaped to %23. I tried [NSURL URLWithString: anchorname relativeT

Re: Using an anchor in NSURL file url

On Jan 21, 2016, at 17:17 , Jeff Evans wrote: > > In OSX I'm using an NSURLRequest to load a file url in WKWebView. Works > fine unless I try to add an anchor to the path, for example, > > [path]/filename.html#anchorname > > The problem appears to be that the # gets escaped to %23. Can

Re: Using an anchor in NSURL file url

Thanks - Here's what I'm doing: Assume a directory called book and a file called chapter1, and an anchor called #page3 NSString *filePath = [[NSBundle mainBundle] pathForResource: chapter1 ofType: @"html" inDirectory: book]; //That file path gets converted to a

Re: Using an anchor in NSURL file url

On Jan 21, 2016, at 7:17 PM, Jeff Evans wrote: > > Colleagues, > > In OSX I'm using an NSURLRequest to load a file url in WKWebView. Works > fine unless I try to add an anchor to the path, for example, > > [path]/filename.html#anchorname The most correct way would be to use NSURLCompone

Re: How to record screen in iOS

Hi, I know I can do this with QuickTime, but the problem is you need a computer with you to do so, I want the users can do it whenever they want. ReplayKit maybe the choice, I will take a look. For the sandboxing reason, I know it possibly not to get it done. However, what if there is some dark ma

Re: How to record screen in iOS

Hello, The feature you’re proposing sounds like malware to me, or could easily be repurposed for malware. Discussing ways to do this with undocumented APIs is borderline ethical and probably not acceptable use on an official Apple mailing list. I think the real answer is there’s no documented

Re: How to record screen in iOS

Is there a reason you can’t use ReplayKit: https://developer.apple.com/library/ios/documentation/ReplayKit/Reference/RPScreenRecorder_Ref/index.html#//apple_ref/occ/cl/RPScreenRecorder I’ve been thinking of exploring this for support purposes (i.e let the user hit a button to record the screen a

Re: How to record screen in iOS

If a 3rd party solution will meet your needs the take a look at https://lookback.io Dave On 21 January 2016 at 19:14, Alex Kac wrote: > Is there a reason you can’t use ReplayKit: > > https://developer.apple.com/library/ios/documentation/ReplayKit/Reference/RPScreenRecorder_Ref/index.html#//apple