> On 28 Jan 2016, at 00:34, Alex Zavatone wrote:
>
> Ahh, just a little testing shows that well, if it’s not ASCII, it’s not going
> to work, period.
See? If it ain’t ASCII it ain’t Source Code! lol
Dave
___
Cocoa-dev mailing list (Cocoa-dev@lis
Apparently you can't in obj-c, but there appear to be a few tricks on the Swift
side of things that are interesting and worth checking out. I saw examples of
using option p as the pi character and using it in an assignment statement.
But this is objective-c so you're 100% right.
Sent from my
On 27 Jan 2016, at 12:30, Dave wrote:
> I find the “_” very difficult to see and also I tend to think of it as “Apple
> Reserved”, which I think it used to be?
Still is, for *methods* so for selectors/properties. However, a single
underscore is fine for instance variables backing a method, and
> On Jan 28, 2016, at 03:14, Dave wrote:
>
>
>> On 28 Jan 2016, at 00:34, Alex Zavatone wrote:
>>
>> Ahh, just a little testing shows that well, if it’s not ASCII, it’s not
>> going to work, period.
>
> See? If it ain’t ASCII it ain’t Source Code! lol
But that was originally said in resp
Now that this is all resolved, the next question - why default to Desktop
instead of Documents? I'd expect Documents, and I hate stuff that clutters up
Desktop - one of the first things I do on new installs is change the default
location of screen captures to Pictures.
__
On Jan 28, 2016, at 1:08 AM, Graham Cox wrote:
>
>> On 28 Jan 2016, at 4:36 PM, Graham Cox wrote:
>>
>> Why would the OS think an app was sandboxed
>
>
> OK, I think I found the problem. In Build Settings->Code Signing, the “Code
> Signing Entitlements” was set to a .entitlements file which
> On Jan 27, 2016, at 22:08, Graham Cox wrote:
>
>
>> On 28 Jan 2016, at 4:36 PM, Graham Cox wrote:
>>
>> Why would the OS think an app was sandboxed
>
>
> OK, I think I found the problem. In Build Settings->Code Signing, the “Code
> Signing Entitlements” was set to a .entitlements file wh
> On 29 Jan 2016, at 4:51 AM, Lee Ann Rucker wrote:
>
> Now that this is all resolved, the next question - why default to Desktop
> instead of Documents? I'd expect Documents, and I hate stuff that clutters up
> Desktop - one of the first things I do on new installs is change the default
> lo
I would think so - it'd be pretty sh*tty if it did! (though I wonder what
you're going to do with the 20% excess cast-iron?)
On Jan 25, 2016, at 11:53 AM, Dave wrote:
> Hi,
>
> Is the PID of an Application 120% cast-iron guaranteed not to change during
> the Application’s life span?
>
> All
IIRC, for Mac App Store apps, your app has to perform copy-protection checking
itself (i.e, receipt checking); Apple specifically didn’t want to do that
themselves so that when the inevitable crack appears in the wild, it doesn’t
take out the whole app store - just the apps that the particular c
> Another approach is to make a vanilla non-AppStore copy of the app available
> to customers on request, if they want to replace the LGPL library. You’d just
> need to find some way for the requestor to prove to you that they bought it
> from the App Store.
>
> —Jens
There have been developer
11 matches
Mail list logo
