Re: NSDocument autosavesInPlace and additional menu items

>> my menu nib contains "Save" and "Save As...” items > > What is the IB action associated with your Save As item? It’s not clear how > Cocoa recognizes the menu item, but the action seems like the likely > mechanism. Or it could be by standardized name, so your old menu might (e.g.) > have

Re: strange behaviour of hasPrefix

On May 3, 2017, at 11:25 AM, Gerriet M. Denkmann wrote: > Why has test2 no prefix? Seems like a subtle difference between the implementations of __NSCFConstantString/__NSCFString and NSPathStore2/NSString. I ran your code and got the same results. I also added a bunch of

Re: Does file-mapping a memory allocation work around RAM limits?

Thanks for that thorough explanation! We're going to try using mmap(). It will be interesting to do this from Swift. > On May 4, 2017, at 10:04 , David Duncan wrote: > > >> On May 3, 2017, at 11:51 PM, Rick Mann wrote: >> >>> >>> On May 3,

Re: Does file-mapping a memory allocation work around RAM limits?

> On May 3, 2017, at 11:51 PM, Rick Mann wrote: > >> >> On May 3, 2017, at 23:27 , Doug Hill wrote: >> >> >>> On May 3, 2017, at 6:21 PM, Rick Mann wrote: >>> >>> Our iOS app works with very large data buffers (hundreds of

UIWebView displays margins incorrectly with black background and paginationMode = UIWebPaginationModeLeftToRight

Xcode 8.3.1, iOS Simulator 10.3 and iOS 10.3.1 I am using a paginated UIWebView to display some HTML. Everything appeared to be working OK until I changed the CSS to set the background color to black and the foreground (text) color to white. Then I found that wherever there is a non-zero

Re: NSDocument autosavesInPlace and additional menu items

On 2017 May 03, at 15:43, Quincey Morris wrote: > > If you can’t figure it out, there may be some IB magic in the File menu that > your XIB doesn’t have because it’s too old. Or maybe your predecessor implemented -menuNeedsUpdate:. I’ve been able to hack

Re: Does file-mapping a memory allocation work around RAM limits?

To answer the OP’s original question, I’m not sure about the exact rules Apple is using on iOS, but I’d expect the memory limit to apply to *private* memory, namely that allocated using malloc() et al, plus dirty pages mapped with mmap()’s MAP_PRIVATE flag. Read-only and shared mappings that

Re: Does file-mapping a memory allocation work around RAM limits?

> On May 3, 2017, at 23:27 , Doug Hill wrote: > > >> On May 3, 2017, at 6:21 PM, Rick Mann wrote: >> >> Our iOS app works with very large data buffers (hundreds of MB). As you can >> imagine, we run into issues at times. >> >> I saw some sample

Re: Does file-mapping a memory allocation work around RAM limits?

> On May 3, 2017, at 6:21 PM, Rick Mann wrote: > > Our iOS app works with very large data buffers (hundreds of MB). As you can > imagine, we run into issues at times. > > I saw some sample code that used this technique, and it got me wondering if > this actually works