macOS 12.6, Xcode Version 9.1 (9B55). A window with: fixedSpace | fixedTextField | fixedSpace | textField(width ≥ 50) | fixedSpace | textField(width ≥ 100) | variableSpace( width ≥ 10) This

Indeed. The only place where I didn’t look. Thanks a lot! Kind regards, Gerriet.

Select the formatter and in the Attributes inspector change the Behavior to OS X 10.4+ Custom. -- Shane Stanley <sstanley@...> <www.macosxautomation.com/applescript/apps/>,

macOS 12.6, Xcode Version 9.1 (9B55). I added a NumberFormatter (Decimal) to some TextField. This now shows: “12.345”. Not bad, but I want to see: “12.3”. NSNumberFormatter has a property:

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