Re: Core Data debugging

On Jul 16, 2009, at 1:58 PM, Bill Bumgarner wrote: Then your macros are buggy. According to the rules now, quite possibly. But the rules are kinda busted. One place that looking at *outError and being able to assume it would be nil on the *entry* to a NSError-returning method is whe

Re: Core Data debugging

hould check for this and help you remember to do it. On Jul 16, 2009, at 4:16 PM, Quincey Morris wrote: On Jul 16, 2009, at 15:54, Quincey Morris wrote: On Jul 16, 2009, at 15:19, Timothy Wood wrote: then at "xxx" you'd like to build a new NSError that has *outError (if outErr

Re: Core Data debugging

On Jul 16, 2009, at 5:39 PM, Greg Parker wrote: The alternative would be to require the caller to set `err=nil` before calling `whateverWithError:&err`. Yes, and this would a code savings. Only at the top level invocations would you need to worry about this. There are far more methods

Re: Core Data debugging

On Jul 16, 2009, at 5:44 PM, Quincey Morris wrote: In the second case, you're not screwed because of "these NSError rules" but because you're using an output parameter of the method as an input parameter to the macro. It's a plain bug, unless you assert it not to be a bug (which is basicall

Re: Triggering an NSTextStorage Bug

On Mar 20, 2013, at 12:01 PM, Kyle Sluder wrote: > The reason it's limited to 19 bits is because for speed purposes > NSParagraphStyle implements its own inline retain count rather than > relying on NSObject's external refcount table. Which is also why you > can't make ARC weak references to NSPa

Re: inspecting undo

On Jul 31, 2008, at 10:03 AM, I. Savant wrote: On Thu, Jul 31, 2008 at 12:52 PM, James Maxwell <[EMAIL PROTECTED]> wrote: AFAIK there's no way to print the whole undo stack, but can I just see the top? There's no public API for directly accessing the stacks (undo and redo), however you c

Re: Adding an NSColor subclass to NSColorPanel?

On Jul 31, 2008, at 2:20 PM, David Springer wrote: I would like to add instances of a subclass of NSColor to the color panel. The problem is, when you change to another app that does not know about this subclass, the NSColorPanel kind of freaks out and shows all the colors as white (even the sy

Re: Sub-pixel font smoothing with CGBitmapContext

On Jan 28, 2009, at 5:15 PM, Slava Pestov wrote: Hi all, When I render text into a CGBitmapContext that has been filled with a solid color, sub-pixel font smoothing is not applied and text looks suboptimal compared to text rendered elsewhere. How can I enable font smoothing? Calling CGContextS

Re: Sub-pixel font smoothing with CGBitmapContext

On Jan 29, 2009, at 10:56 AM, David Duncan wrote: Its been a while since I last looked at this, but I think the context's format needs to be native endian (add the kCGBitmapByteOrder32Host flag). Heh; I totally would not have expected that from the name or docs. But, adding a case like

Re: Sub-pixel font smoothing with CGBitmapContext

On Jan 29, 2009, at 12:41 PM, David Duncan wrote: Yea, its not documented, and its probably more of a quirk of the font rendering than anything else. It works today, and primarily I offer the solution because if it stops working in the future, the worst that will happen is you will get text

Internships available at The Omni Group

We’re looking for one or two software development interns for this summer! Check out our open positions at for more info on internships or full-time employment. -tim ___ Cocoa-dev mailing list (Cocoa-d

Re: CALayers Lost After Switching Window's ContentView

On Feb 16, 2009, at 12:45 PM, David Duncan wrote: The simplest solution, if you can mange it, is to set the view's layer to your own layer, at which point AppKit will take a hands off approach and allow you to determine when the layer should go away. We are also mixing hosting & backing a

Re: NSURLConnection and HTTPS

On Oct 3, 2008, at 8:17 AM, dexter morgan wrote: Searching inside the list I've found this code: [_request setAllowsAnyHTTPSCertificate:YES forHost: [_url host]]; It's a private API. Unfortunatly the message is too old (2005) and at this time this method seems to be removed. Anyone can

Re: How do I debug weak_unregister_no_lock?

On Jan 15, 2014, at 12:14 AM, Gideon King wrote: > I tried putting a dealloc in my class and nilling out everything, but still > got the problem. I then added >self.inspector = nil; >self.parentSlice = nil; > to my dealloc, and since then I have not been able to reproduce the problem >