Well, I think I have bumbled my way towards a working solution that seems to
work (tested on OS 10.9), although this was largely through trial and error and
so might not be the best way of doing things. Thankyou very much to everyone
who offered help on and off list.
One indirect clue I found w
Just thought I’d like to warn everyone about something:
In the past, the NSFoundationVersionNumber constants for the same major OS
version always used to have the same integer component. For example, the
constants for 10.8, 10.8.1, 10.8.2, 10.8.3, and 10.8.4 are 945.00, 945.00,
945.11, 945.16,
> On Jul 9, 2015, at 9:20 PM, Quincey Morris
> wrote:
>
> Amazingly, this change seems to have made it into beta 3. I didn’t see it
> mentioned in the release notes, though it’s big news!
Did it?? In beta 3 I’m still getting the error “All stored properties of a
class instance must be initia
On 10 Jul 2015, at 12:01 pm, Charles Srstka wrote:
> What this means is that if you try to use an El Capitan-only feature and put
> it in a block that starts with a check on floor(NSFoundationVersionNumber) or
> floor(NSAppKitVersionNumber) to make sure it’s larger than the value for
> 10.10.0
On Jul 10, 2015, at 7:31 PM, Ben Kennedy wrote:
>
> On 10 Jul 2015, at 12:01 pm, Charles Srstka wrote:
>
>> What this means is that if you try to use an El Capitan-only feature and put
>> it in a block that starts with a check on floor(NSFoundationVersionNumber)
>> or floor(NSAppKitVersionNum
