Thanks a lot, seems to have cured things. I added a line to set the window delegate to nil before [myWindow close] and things are ok now. ---markus---

Kurt, The menu key equivalents are pulled out before -keyDown: is called. You can override that event in -performKeyEquivalent:, a methof of NSResponder (and therefore views, etc). You can probably

Sometimes I get the following message logged when by app quits: *** _NSDocumentBasicAsyncOperation 0x600003e25a00 went isFinished=YES without being started by the queue it is in It seems to be

There’s not really enough information here to really solve the problem. The overall “feel” of the crash is a memory management problem related to the various objects used alongside a NSWindow.

I don’t know exactly *which* typographic problem is intended to be solved by line fragment padding, but the most likely one is that various letters may extend outside their layout boxes. The layout

OK, as usual after writing a lengthy question, it helps focus the mind on what’s really going on, and minutes later the solution materialises. NSTextContainer has a property called

Ignore this part - on further test this is working correctly.

Hi all, I’m wrestling with annoying inconsistencies in the various options for text rendering. Here’s what I want to do - I want to draw overbars above runs of characters in a text string. This is

Sorry for the delay. As this is a pet project it had to stay in the back for some time now. Only today did I find the time to play with the app again and copy a crash dump. How I'd do this in Xcode or

I don’t have experience with keyboard extensions, but with some other types. I have *not* being successful in stepping through extension code, because (apparently) the system doesn’t know that the

Hi all, I run a software company in the UK and we're looking to hire some full-time Mac software developers to join our growing team in Edinburgh, Scotland on a permanent basis. We'll be advertising

Anybody else have problems with developing iOS keyboard extensions not working? I've barely added any code except a Next Keyboard button, figured out how to attach Xcode to the keyboard target after

And further, if I remove the __weak qualifier, it works without a breakpoint... OK, this code is from years ago, and I no longer know why the reference to the open panel had to be weak. It is used

Why are you declaring this __weak? That means the open panel is subject to *immediate* deallocation, which sounds exactly like the symptoms you’re seeing.

A little more investigation reveals that it seems that the key thing is actually setting a breakpoint and stepping over the line: __weak NSOpenPanel *openPanel = [NSOpenPanel openPanel]; in the

I have a weird situation where I show an open panel via beginSheetModalForWindow:completionHandler:. The problem is that it works OK with Mojave (and before, I assume), but it doesn't work in Catalina

On Sat, 9 Nov 2019 14:37:55 +0100, Markus Ruggiero said: Have you tried various debug tools like guard malloc, address sanitizer and thread sanitizer? Sean

Stack trace of the crash?

Thanks, tried it but did not help. The box was checked, tried both ways, same crash.

Sounds like you have ‘Release When Closed’ checked in you XIB/NIB for the window. Try unchecking it. Click the XIB/NIB in your project navigator and hi-light the window in question in the tree