Thanks for the input, everyone. I mentioned that exclusionPaths are used, so the text flows inside arbitrary shapes, mostly comic book balloon type blobs. As such, there's rarely a straight bottom

This is what we do in a drawing app, which works well for us. When the text box is selected, it shows the + symbol as part of the frame. If not selected that’s not visible, so the text itself

Quincy, your observation reminds me of how Quark Xpress handled this in circa 1989. It was a surprisingly nice indicator that “there is more to this text box”. I think they may have put a small

Yes, that sounds correct. I was thinking that there was a problem for the original caller (the one in whose stack frame the block resides), because the block might have moved after the call returns.

In text layout apps that I’ve used, which can flow text through multiple containers, there’s typically a small box outside the top-left and bottom-right corners of the container frame. The boxes

I'm using NSTextContainer with exclusionPaths, NSLayoutManager, and UITextView for rendering text into balloons, and the user can control the font size. When overflow occurs, I'd like to show an

No, because then blocks would always be copied to the heap, even in common cases where they don’t escape, like calling NSDictionary’s -enumerateKeysAndValues: method. That would make these a lot

I think that should be an “or”: if you assign it to a non-local variable *or* pass it as a parameter. That’s because the block is implicitly moved to the heap (which is what a copy does) if the

I think ARC copies the block automatically if you assign it to a variable instead of just having it as a parameter of a function/method call. (A block really only gets copied once; it’s more like

Makes sense, but there’s a bit of a problem. To do that I’m going to have to create the block and keep a reference to it. That doesn’t seem to be how the GCD dispatch code snippet works - it

Oops, sorry, that was weird. Mail sent that message when I just closed the window, which wasn’t what I intended to happen. I was in the process of composing an extremely witty response, but it

Perhaps. :)

Oh wow, I didn't know about that method -- perhaps because my code predated 10.6. :) --Andy

If you mean “cancel” in the sense of “prevent it from starting”, then the answer is yes, you can use

Hi Gerriet, Try this: BOOL didSelect = [[NSWorkspace sharedWorkspace] selectFile:filePath inFileViewerRootedAtPath:containingDirPath]; -Andy

Hi all, Is there a way to cancel a scheduled block used with dispatch_after(…)? While I’m finding the functionality it offers really useful, it seems like as soon as you use it you have to

I just tried it again, and now Xcode told me that: “ Action ‘boxClicked:' sent by 'Check Box' is connected to 'File's Owner,' an invalid target (Objects inside view based table views may only be

It does indeed. Thanks very much for telling me. Kind regards, Gerriet.

Though in concept, I love the idea of KV observers, in practice, I’ve found that they lead to too many crashes. I’ve switched over to sending notifications and it’s much less to worry about and

Gerriet, I am doing the same thing now on iOS. Here’s what I am doing and am open to better approaches. Being able to do this requires a special set up where the cell contents are retrieved from