Have you tried -URLByResolvingSymlinksInPath? As far as I’m aware, the Pictures
entry inside your container is a symlink to the real thing, so assuming you
have appropriate entitlements, should be possible to resolve it.
Mike.
> On 11 Dec 2022, at 10:56, Gabriel Zachmann via Cocoa-dev
> wrote
It’s not a very good fit, but when you say a “GCD concurrent queue”, you’d need
to be more specific. There are several configs possible. Do you mean a global
queue, or one you made yourself? If you made it yourself, how did you configure
it?
The tricky problem is that GCD aims to optimise CPU u
Perhaps worth noting that the docs for commonPrefixWithString:options: cover
cases like this:
> Discussion
> The returned string is based on the characters of the receiver. For example,
> if the receiver is “Ma¨dchen” and aString is “Mädchenschule”, the string
> returned is “Ma¨dchen”, not “Mäd
If I remember correctly from doing something like this in the path, the
important thing in the below code is you are providing a custom image for the
nav bar to draw as its background, instead of doing a blur effect. The image
you supply happens to be empty so nothing is drawn in the end, and yo
Your description seems a bit confused here.
Why declare the applySketchShadow() method but never use it?
The force conversion of UIBezierPath to CGPath smells, and suggests you never
hit this code path. If so, I think you may have layers with no content and no
path, so will not generate a shado
NSBeep() ?
Mike.
Sent from my iPhone
> On 11 Jun 2021, at 13:59, Gabriel Zachmann via Cocoa-dev
> wrote:
>
> Sorry for the stupid question:
> what would be the easiest way to produce that "tick" system sound
> signifying an invalid keyboard input?
> I am talking about the new system sound un
> On 10 May 2021, at 10:52, Mark Allan via Cocoa-dev
> wrote:
>
> Hi,
>
> Now that Alex has the answer to his problem, can I ask a follow-up question
> based on this line in his initial email?
>
>> On 9 May 2021, at 1:12 am, Alex Zavatone via Cocoa-dev
>> wrote:
>> _configurationDic
Further to earlier answers, it’s worth pointing out you’ve got an anti-pattern
in this code. You go:
1. Check if file exists
2. Try to read file
There is no point to step 1. Just do step 2 directly, and handle failure there.
If you _don’t_ handle failure at step 2, you’ve got yourself a nasty l
> On 3 Apr 2021, at 16:34, Richard Charles via Cocoa-dev
> wrote:
>
>>
>> On Apr 3, 2021, at 8:59 AM, Gabriel Zachmann wrote:
>>
>> Thanks a lot for your response!
>>
>>> How about something like this?
>>>
>>> NSUserDefaults *monitor1 = [[NSUserDefaults alloc] init];
>>> [monitor1 set
This does seem quite surprising. However, here’s the thing: this code is very
strange approach to take.
Number 1: Cocoa doesn’t support exceptions as an error-handling mechanism
except where explicitly stated and supported. You’re trying to use them, which
is asking for trouble. The system does
CADisplayLink
Mike.
Sent from my iPhone
> On 15 Oct 2020, at 20:13, Andreas Falkenhahn via Cocoa-dev
> wrote:
>
> I'm drawing inside an NSView by simply setting its layer's contents to a
> CGImage which is updated for every frame, e.g. something like this:
>
>dp = CGDataProviderCreateW
Correct, this is your issue. Have a read of the docs on +[UIImage imageNamed:]
They explicitly discuss the cache. This is not the API you want.
Mike.
> On 23 Sep 2020, at 02:12, Eric Lee via Cocoa-dev
> wrote:
>
> Ah maybe it is the use of `imageNamed:`. I believe that caches the image
>
> On 13 Nov 2019, at 19:31, Turtle Creek Software via Cocoa-dev
> wrote:
>
> I made a rather bold statement about Cocoa being doomed. Here's some
> background on where it came from.
>
> Apple and Microsoft are both working on next-generation app development
> platforms, with the goal of havi
> On 27 Sep 2019, at 00:43, James Walker via Cocoa-dev
> wrote:
>
> On 9/26/19 4:20 PM, Gabriel Zachmann via Cocoa-dev wrote:
>>> The issue in the below code to my eye is that you allocate a path with
>>> CGPathCreateWithRect (+1) but then don't release it.
>>>
>>> In that case, I am wonderi
I don’t believe that’s entirely true. “make” methods return a +0 value.
The issue in the below code to my eye is that you allocate a path with
CGPathCreateWithRect (+1) but then don't release it.
Mike.
> On 26 Sep 2019, at 17:16, Glenn L. Austin via Cocoa-dev
> wrote:
>
> The analyzer is gre
> On 17 Sep 2019, at 09:04, Gabriel Zachmann via Cocoa-dev
> wrote:
>
>>
>> The bounds origin is the origin of the coordinate system for sublayers of
>> that layer, and thus changing the bounds origin moves sublayers around.
>
> Thanks a lot for the insight.
>
> Just out of curiosity (or f
16 matches
Mail list logo
