Flutterby™! : If a Cocoa API isn't working

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

If a Cocoa API isn't working

2019-05-08 18:40:07.222101+02 by Dan Lyke 3 comments

If a Cocoa API isn't working, it may be that you're just not calling it enough. Wrapping [view setFrame:...] in a for(...) loop is an OS/X idiom that can solve your problems... #onlyhalfkidding #maybenotevenhalf #onlyaquarter...

[ related topics: Interactive Drama Work, productivity and environment ]

comments in ascending chronological order (reverse):

#Comment Re: If a Cocoa API isn't working made: 2019-05-08 19:57:58.903538+02 by: markd

dispatch_async(mainqueue, ^{ do something that's otherwise misbehaving }); is also a common idiom

#Comment Re: If a Cocoa API isn't working made: 2019-05-09 01:51:33.186941+02 by: Dan Lyke

In particular, this is about an NSOutlineView delegate -outlineView:viewForTableColumn:item and setting the font and size of an NSTextField retrieved from makeViewWithIdentifier:. The first time an outline section is opened up it doesn't work, the second time it works fine. Sigh.

#Comment Re: If a Cocoa API isn't working made: 2019-05-10 17:36:12.769173+02 by: markd

NSOutlineView has always been a bucket of suck.