This works but it’s not right and throws a yucky message let holdDoc = try NSDocumentController.shared.openUntitledDocumentAndDisplay(false) as! Document // set the updated

Hi, I have a metronome app that is able to play audio in the background just fine. It even continues playing when the screens is locked. That is, until the screen goes dark after a few seconds.

I have an App that needs to be upgraded (thanks App Store) and I want the new App to Open and migrate it’s old documents to the new versions document. With the new File Type and Extension. All

I don’t have any detailed list of what changed in Xcode 9.3 that I can share, sorry. Speaking generally, the only changes anyone should notice should be positive; much of the underlying

Any pointers to information on what changed? I looked through the Xcode Release Notes

To answer my own question: textField.stringValue = someString; When I look at the attributedStringValue I see Generic Gray colorspace 1 0.5 So I do: NSMutableAttributedString *mus = [

I have an NSTextField (macOS 13.4, Xcode Version 9.3 (9E145)) which says: textColour Generic Gray colorspace 1 1 backGroundColour NSCalibratedWhiteColorSpace 0 0.4 This, I guess, means all white

The main idea for Cocoa localization is that your source artifacts are the “the truth” for your development region (by default English): You use the real strings in NSLocalizedString() macros and

I have an app (macOS 13.4, Xcode Version 9.3 (9E145)) which was localised (Xcode did some magic for me). Now I made some changes. Is there a way to update the Localizable.string, MainMenu.strings,

On Fri, 27 Apr 2018 11:57:15 +0700, Gerriet M. Denkmann said: See also: <http://sealiesoftware.com/blog/archive/2012/2/29/objc_explain_return_value_of_message_to_nil.html> Sean

Yes: https://developer.apple.com/library/content/documentation/Cocoa/Conceptual/ProgrammingWithObjectiveC/WorkingwithObjects/WorkingwithObjects.html#//apple_ref/doc/uid/TP40011210-CH4-SW22 “Working

macOS 13.4; Xcode Version 9.3 (9E145). This is (I believe) documented to work: NSString *answer = … if ( answer.length == 0 ) { // works for answer = nil or answer = “” (empty string) answer

Hello All, I’m looking for remote work on Mac and iOS. I have over 25 years experience on the Mac and iOS since the first iPhone. I’ve recently finishing a long contract where I gained a *lot*

DOH. I think it’s time for me to update my glasses prescription. Thank you.

I haven't tested this, but I would imagine that it produced no line endings at all (i.e., a string containing only base64 alphabet). No it doesn't: The enum defines a bit mask. The above declaration

From the docs: Discussion By default, no line endings are inserted. If you specify one of the line length options (NSDataBase64Encoding64CharacterLineLength or

Xcode 9.2, iOS 11.2, Objective-C Looking at the header for NSData, and base64EncodedStringWithOptions: NSDataBase64EncodingOptions, the options are these starting on line 50 of NSData.h: typedef

Apparently Xcode has become Windows 95. When in doubt, reboot. : /

Xcode 9.x has an intermittent bug where it gets confused about what you’ve changed. (It looks like the actual displayed text is inconsistent with some internal memory representation.) It doesn’t

Perhaps I’m expecting too much from Xcode. I’d quit and relaunched in order to get output for the code I’d posted. I didn’t expect I’d have to quit and relaunch again because I changed one