Well, by default, NWView coordinates are flipped vs. CGContext coordinates. I suggest you try temporarily forcing the point you’re drawing at to be the center of the context or view, and see if the

I need to replace calls to CGShowTextAtPoint() with calls to -drawAtPoint:withAttributes: I made this change and drawing fails… :/ i.e. no text rendered, no exception, logging of errors, etc.

Oh interesting - it looks like when you call [NSAlert beginSheetModalForWindow:completionHandler:], the alert gets retained by the parent window's attachedSheet property. So you're right, no issues

That is the case I’m talking about and no, it works fine even if you don’t “worry” about the lifecycle. Just alloc + init + autorelease, then beginSheet…. it works, it has always worked

You're making this far more complicated than it is (talking about running the alert asynchronously, etc). NSModalResponse choice = [alert runModal]; will run the alert synchronously. Note that it

That’s exactly what I’m saying - you are taking ownership of it with alloc+init. Then you release it or autorelease it within the scope of setting it up. Normal rules. But the point is the alert

The MRR rules are straight forward and deviating from them because the runloop may retain the alert is asking for trouble in my opinion. There is no harm in taking ownership of the alert and

Thanks Graham and Alex. I had reached the same sort of conclusions - but could not find any corroborative info anywhere .... Peter

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