I think it’s installing components that allow access to devices. I have no idea what’s modified. No. [1] contains a complete Unix C build environment (tools, headers, libraries) that’s used when

After migrating to macOS 13.1 when I first started Xcode (9.1) it told me that it had to install some components. What are these “components” and where do they live? Also: My macOS 13 partition

Starting an document based app in macOS 13.1 I get: […] [default] [ERROR] Failed getting container for URL: [ ~/Desktop/the current document] r, error: Error Domain=BRCloudDocsErrorDomain Code=12

You need to subclass NSClipView and implement the behaviour there. It’s annoying that there’s no built-in solution since it’s an ‘obvious’ requirement to me. The better news is that the

I don’t think there’s any magical solution. From what I see in Preview, it has a 2-phase approach — it lets you zoom normally via a pinch gesture (that is, doesn’t force any centering), then

Hi Brandon. One other consideration with iOS is that you may need to whitelist the destinations you want to connect to by declaring them in your info.plist under the NSAppTransportSecurity key. I

Just take a look at the header. It’s only the older version that takes an NSHost that’s deprecated: @interface NSStream (NSSocketStreamCreationExtensions) +

Ack. I'm having a hard time figuring out how to make an NSImageView in an NSScrollView act like it does in Preview.app, where it will stay centered within the window when any axis is smaller than the

Jens, Thanks for reply. I thought the +[NSStream getStreamsToHostWithName:…] was deprecated in iOS 11+? --Brandon

Consider using NSURLSessionStreamTask; it’s higher-level with IMHO a better API, and it supports proxies. If you’re using an NSURL for this, I don’t think you’re doing it correctly. URLs have

All, I created a simple iOS app to connect to a server and receive a message. I am doing this as an example app using InputStream, OutputStream, and StreamDelegate. The Server is a simple Java app

The way I always do this: - create a weakSelf, then in the block assign it to a strongSelf, and test strongSelf for nil - have a property on your class "delayedBlockCancelled" (you can use an ivar

I'm not sure where my brain was, but I totally blanked this out and was too focused on trying to roll my own. This works just fine in my scenario, even when oddly shaped exclusionPaths are applied.

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