Re: Documentation Workflow

2016-12-02 Thread Slipp Douglas Thompson
Alternatively, there's always archive.org's Wayback Machine. For example, the Core Data Programming Guide from 2014-07-03 is available right here:

Re: Documentation Workflow

2016-11-17 Thread Slipp Douglas Thompson
re again, hosted externally: Turns this: https://cl.ly/0m1c462d1z40 Into this: https://cl.ly/2b03340B3F2y — Slipp > On Nov 17, 2016, at 8:55 AM, Richard Charles <rcharles...@gmail.com> wrote: > > >> On Nov 17, 2016, at 6:45 AM, Slipp Douglas Thompson >> <apple+co

Re: Prioritizing drawing of the important stuff

2016-10-29 Thread Slipp Douglas Thompson
You could just set up a simple debounce timer— reset it back to 0sec elapsed time whenever the slider is updated, and if it reaches a small delay then the HQ image is rendered (and remains on-screen until the slider is later moved and the process repeats). No need to rely on GCD or threading.

Re: Stupid objective-c question

2016-09-26 Thread Slipp Douglas Thompson
I'm just going to throw this out there as a solution, not because I recommend this approach (it's API misuse after all) but because it would work. Instead of using an `NSString *` you could use a `SEL` (AKA `struct objc_selector *`) since SELs are guaranteed to be unique for each given string

Re: Stupid objective-c question

2016-09-21 Thread Slipp Douglas Thompson
> On Sep 21, 2016, at 8:00 PM, Slipp Douglas Thompson > <apple+cocoa-...@slippyd.com> wrote: > >> On Sep 21, 2016, at 17:01 , Graham Cox <graham@bigpond.com> wrote: >>> >>> This should be: if([(NSString*)context >>> is

Re: Stupid objective-c question

2016-09-21 Thread Slipp Douglas Thompson
> On Sep 21, 2016, at 17:01 , Graham Cox wrote: >> >> This should be: if([(NSString*)context >> isEqualToString:@“mediaLibraryLoaded”])… > > Actually, this is not a good idea either, because *other* observations — ones > you don’t control — might use a value that’s not

Re: Stupid objective-c question

2016-09-21 Thread Slipp Douglas Thompson
> Whenever I have two string literals @"XYZ" at different places in the same > compilation unit, > and the XYZ are identical, then the compiler (or the Objective-C standard) > make sure that > the pointers to those literals are identical? > > In other words, the compiler unifies the two