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

Way back when I dabbled around with ObjC (that was in 2002!) I created a small app that shows images from disk. About a year ago I upgraded this app to 64bit and ARC. This went well after a bit of

I played with this a bit more. It turns out that the bug is “transient”, in the sense that if you quit Xcode and relaunch, it picks up the correct deployment target.

I'm glad I could help. It's just one of those things I've run into myself a million times - I _think_ I've checked all my assumptions when I'm debugging something, and end up off in the weeds (for

Hi Jon, Turns out you’re right - the images were NOT square - they vary. It just so happened that the first image in my selection was square, and that’s what I observed in the debugger. Since it

I’m just relating what I’m observing in the video. Each icon is getting stretched vertically not by a uniform factor, but so that the drawn elements exactly fit the given bounds. Honestly, it

Hi Jon, The images are square - the rect returned by -imageRectForItemAtIndex is used to render them in the view as well as supplying the frame to the NSDraggingItem. That’s why it seems odd to me

Oh, my bad. I mean the drawing code within libItem.previewImage. - Jon

Judging from the video, your images are not square. It looks like they're only as large as they need to be to contain the drawn item, and are getting stretched to fit your square NSDraggingItem

I’m modernising some old code that does drag and drop the old, simple and perfectly functional (but deprecated) way. The new way seems twice as complicated to me, but hey-ho. Anyway, I’m creating

Hmmm, oh well, I guess I’ll just live with it. Bigger fish to fry and all that. Thanks! —Graham

I see similar results. It looks like a bug. If I set “Builds for” to “Deployment Target”, it shows the wrong deployment target (10.13 instead of 10.11), or if I choose a popup setting later