I stopped on that breakpoint as well, and it doesn't help other than point out that it is indeed a bug. Changing the bound value should not cause editing to end. I just want to know if it's been fixed

IIRC, there is another method that you can check, with something like didEndEditing something like that. I remember having to go through several on iOS to find what I wanted.

Since we finally were able to move up to 10.13 (printing company, historically slow to change), I've noticed that text fields in views and in cell-based table views now exit editing as soon as any

Dear all, Thanks for your replies. It turned out it wasn't due to a zombie pointer, though I did turn on that setting to check (hadn't thought of that as a possibility for this problem). After quite a

Oh - here you go. It's in the scheme's Run > Diagnostics tab even back in Xcode 6: https://code.tutsplus.com/tutorials/what-is-exc_bad_access-and-how-to-debug-it--cms-24544 - Jon

As Quincey said, it looks like you've got a zombie pointer that's now pointing to an NSWindowGraphicsContext instead of the original, now-deallocated NSSnapshotBitmapGraphicsContext. Turn on zombie

I suggest that you start with most mundane possibility, that this is a zombie object. My guess is that this is one of those crashes that can happen when breaking down a UI, such as when a window is

Hi all, Can anybody advise on the following exception/crash that I am encountering? The issue is: The problem is that as far as I can see this is something internal to AppKit, and I’m not sure what

This is a Swift usage question. I am working on a family of UI objects which share some common behaviors. Having done several, it is time to refactor (for all of the obvious reasons). I would like to

I will file a bug. The reason for using Xcode 9 is that there's a library that depends on the GNU stdc++ library, and the effort to bring that into Xcode 10 is too much to bother at this point. I

It could only be an issue while using the debugger; is there a reason for not using a more modern Xcode? Regardless, you should definitely file a bug report, including a sysdiagnose, your log from

I should add that it's a window in my app, not in Xcode. Running outside the debugger, it appears to be fine, but the exception stops me being able to check on some other issues related to the

Nobody? Here's the backtrace, if it helps: 0 AppKit 0x00007fff29b3657e -[NSWindow(NSDisplayCycle) _postWindowNeedsDisplayUnlessPostingDisabled] + 1964 1 AppKit

Okay, I've got it. The problem was that I was calling OperationQueue.main.addOperation(..) from an Operation. And that call was both capturing "self" and was the last piece of work in the Operation's

Yes, that was my thinking as well. But, the UI was not frozen. (And, indeed, if it had been frozen, I wouldn't have expected the Notification approach to work either.) One additional piece of

Running Xcode 9.4.1 on macOS 10.4.2, when I click on a combo box in a window, in the debugger I get an exception: Nothing appears to be complaining about ambiguous constraints, and searching for that

The only reason I can think of that the first two attempts wouldn’t work is that the main thread’s runloop is blocked, so it can’t process queued blocks. Are you by chance doing something on the

Let me start by saying I have a solution to my problem, but would like to know why some of the other things I tried didn't work... I have some procedures which are performed on background queues

I can't seem to find a way to handle the dark/light versions. Trying iconutil with a system .icns file just gives me the regular ones. So, to make life simpler, I'll just ignore the dark versions and

Why no alpha? Also, just enter man iconutil. More details. https://stackoverflow.com/questions/46428673/iconutil-not-working-on-macos-high-sierra?rq=1 Lots