Normal rules require that you either autorelease it or release it when you’re done (assuming manual MM of course). If no autorelease or release was required, then that would be an exception to

Sorry, A bit groggy here. If my previous assumption that autorelease isn’t needed is incorrect, then it might be that the instance will be retained until the reference to it is cleared or the

Hi Peter, FWIW, I’ve always done exactly the same as this too, and have never had an issue. My understanding (which may be wrong) is that the modal loop that runs the alert temporarily retains it,

My expectation is that autorelease is not needed. In any case, if you do use the memory graph debugger to see if it stays allocated or not, and if autorelease is needed, please let us know.

Why are you making it autorelease? Run your method, display and dispose of the alert and then while your app is still running click on the Memory Graph Debugger icon in the debug bar. Look at your

Thanks Sandor. My use of alert is very tightly scoped - and only used once - and not passed on. Many thanks for the link. Peter

Peter, You may have to dispose of it yourself or maybe ARC will take care of it for you. If you’re writing MRR (not ARC) code you always have to -release/-autorelease objects you own (create).

Hi There I see from the docs that when you create an NSAlert that you should dispose of it yourself. My code for creating a simple alert and using it looks like this :- NSAlert *alert = [[[NSAlert

And I found the missing piece. I was failing to set translatesAutoresizingMaskIntoConstraints to false for one of the views. Doing that makes it all work. John

Further digging leaves me more confused. Because I'm supporting 10.9, there are various features I can't use, so I'm stuck with the auto layout basics, and it's hard to find a good explanation of how

I have my web view displaying correctly, but I've run into a problem in getting the auto layout constraints working correctly. Basically, I build the appropriate web view as a subview of a custom

Thanks for all the tips. I have it all worked out now. John Jens Alfke wrote on 7/2/20 21:39: -- John Brownie Mussau-Emira language, New Ireland Province, Papua New Guinea Kouvola, Finland

You'll need two code paths, one that instantiates and runs a WebView, the other that instantiates and runs a WKWebView. Their APIs and functionality are not identical, so it's not just a question of

Yes I could have been more specific, everything worked, all be it with warnings, with both classes of web views being instantiated in code. Sandor

Yes. Prior to 10.12, WKWebView was not available in Interface Builder and could only be instantiated in code. -Owen

I should note that, once I put the WKWebView into the window, there is an error that I hadn't noticed before: error: Class Unavailable: WKWebView before macOS 10.12 (NSCoding support was broken in

Thanks for the reply. Sandor Szatmari wrote on 6/2/20 20:51: I'm still on 10.14.6, Xcode 11.0, current SDK, which I assume is 10.14 (I can't see an option to choose anything but a platform in the SDK

What SDK are you building against? I assuming deployment target of 10.9 and not earlier… What is the exact problem your having? Is it just warnings, or are there compile/link/runtime errors… I

Does anyone know if it is necessary to dispatch_suspend/resume a queue or source when sleep/wake notifications triggered in a macOS app? I've read the docs and done some searching but couldn't find

My app currently supports 10.9, and I want to add a feature that displays an HTML document stored locally (in the bundle). The obvious way is to have a window which contains a web view. However,