On 06 Aug 2015, at 15:36, Juanjo Conti wrote:
> I've checked the number of entries and is only 350. They are regular
> cookies for well known sites like google, new relic, twitter...
That should not be a performance bottleneck. How often are you calling this
(let's call it saveAllCookies for la
I think you're right on both counts.
I will post this weekend about my solution to the other problem I posted about
-- how to make collapse and uncollapse work both from a toggle button and by
double-clicking or dragging the divider. It turns out that the frameworks use
two different techniques
> On 8 Aug 2015, at 14:06, Bill Cheeseman wrote:
>
> I think you're right on both counts.
>
> I will post this weekend about my solution to the other problem I posted
> about -- how to make collapse and uncollapse work both from a toggle button
> and by double-clicking or dragging the divider
On Aug 8, 2015, at 8:35 AM, SevenBits wrote:
>
> No, I’m afraid that didn’t work. Here are the constraints following your
> suggestions:
>
> — Align Center X to Superview
> — Trailing Space to Superview >= Default
> — Leading Space to Superview >= Default
> — Top Space to Superview Equals Defau
> On Aug 8, 2015, at 9:31 AM, Mike Abdullah wrote:
>
> One thing you might want to watch out for that caught me out:
>
> Although NSSplitViewController is documented to be the split view’s delegate,
> I found that — at least for controllers created in IB — that relationship
> isn’t actually ho
Let's stipulate that _Nullable and _Nonnull are great to have because they can
catch bugs and express API intent better than before, so we want them. The
question is where to put them?
_Nullable and _Nonnull make perfect sense to specify in the @interface. Since
those annotations existing in t
