Hi Graham, Are you setting needsDisplay for each of the subviews? Jeremy

Thanks for having a look, I see what you’re saying, but IB has to instantiate the view (at least once) to capture what it renders. It must also redo this capture whenever any of the properties

AFAICT it doesn’t work like that. The canvas isn’t showing the view hierarchy, it’s showing the objects in the design hierarchy that you can reveal on the left. Of course, that represents the

Hi all, I’m working on a small custom view project (Mac), and have it working generally quite well. I decided to make it IB_DESIGNABLE, and that too mostly works - I can see the view in IB rendered

(I tried to find Charles’s post about this, but didn’t succeed.) Everything you said after the first sentence is absolutely true. That is the standard way, and your suggestion helped rewrite the

I disagree that it's dangerous. It's the standard way code is written when a parameter is passed back by reference. How many times in Apple code do you see something like: NSError* err; if([thing

So, here’s what’s going on. It’s a bit messy. — A pointer has an ownership attribute, which is __strong by default, but can be explicitly specified as __weak or __autoreleasing. In your code,

Excellent. Works perfectly without complaints from the compiler. Thanks a lot! Kind regards, Gerriet.

Yes. Why not this? NSString* s; NSUInteger c = [self computeFor:42 reason:needReason ? &s : nil]; -- Steve Mills Drummer, Mac geek

I have a method like (macOS 13.3, Xcode 9.2 (9C40b)): - (NSUInteger)computeFor: (NSUInteger)arg reason: (NSString * __autoreleasing *)reason { NSUInteger value; // some computing… if ( reason

https://developer.apple.com/library/content/technotes/tn2265/_index.html https://developer.apple.com/library/content/technotes/tn2265/tn2265_PersistentConnectionLogging.zip Testing on the Mac to see

For whose benefit is this rant? We all agree with you. -ben

Argh. Thank for, Glenn. Oh, it would be OH SO NICE, if the docs and the header files actually indicated this to be the case. The current documentation and comments are DIRECTLY MISLEADING. It’s

That's correct. There's no "numeric keypad" for the iPad. -- Glenn L. Austin, Computer Wizard, AustinSoft.com

Doing that did indeed make it work. I ended up with 3 animate/completion blocks: 1. Do the zoom/scroll. 2. Fade the bez in very quickly (0.001). 3. Fade the bez out. I appreciate that Apple has

Just checking in to see if someone here knows something I don’t with regards to the available keyboard types vs. the displayed keyboard types on the iPad under iOS. Of course, the documentation here

Can you dump the properties of the object you are trying to animate and the view before and after each attempt? What thread is this happening on? Anything else besides thread 1? A year back, I

I don’t know, but your code made me wonder what happens (if you haven’t tried it already) if you remove this line from your completion handler: and add this variation to the initiating animation

I'm probably missing something obvious here. I have an NSScrollView. Its document view is an NSImageView. At some point, I add a custom NSView subclass as a subview of the image view. This custom view

Thank you, thank you, thank you - I had just about resigned myself to having to subclass NSTextView and tracking the mouse etc. The issue with its not showing the tooltip the first time is a bit