As Allan suggested, maybe you should post the actual code. I have this same usage in my code and it builds & runs just fine. Regards Sak

Both "plain" and "fullwidth" sort of work; my mistake was using IB to set this property and it had no effect. When I set it in code (thanks, Shane!), I could see differences in behaviour. Both styles

On 27 Mar 2021, at 2:41, Sandor Szatmari wrote: […] This is outlined in pseudocode below. There is nothing conceptually wrong with what you sketch in your pseudo-code. Please post an actual

Thanks Sak, This is how I’m working around the error right now. Like this I get a compiler warning, method not found, return type defaults to id. Port = (NSUInteger)[self.dataSource

serverPort isn't a property, so you have to use [self.dataSource serverPort]; If you want it to be a property, make it so @protocol dataSrcProto @property (readonly) NSUinteger

I have a server class which is abstracted to receive it’s final configuration from it’s data source. The idea is you instantiate the server set the data source and then start the server. During

I had set the style to "full-width" in IB, but that had no effect. Let me give "plain" a shot. Thanks for the suggestions, Sak

I ran into this when updating all of my apps for Big Sur. You'd think the "Full Width" style would make the table, well, full width, but it doesn't. I think the solution was to set the tableview style

Try adding this to your code at an appropriate point: if (@available(macOS 11.0, *)) { myTableView.style = NSTableViewStyleFullWidth; } -- Shane Stanley

The tableviews in one of our apps is behaving strangely when running on macOS 11.x. I have managed to reproduce thsi with a simple test app. Essentially, the issue occurs if if I build using the 11.x

Try surrounding the call with beginEditing and endEditing on the text storage. If it still happens, submit a feedback to Apple with the full crash log. -- Gary L. Wade http://www.garywade.com/

What's the architecture of the machine on which exceptions aren't being caught? Is the try block working on Intel and not on M1? The crash is happening as the RTF reader is setting up the tab stops

Hi folks, Some users are reporting a crash that I can't reproduce, and in an attempt to gain additional diagnostics from a user, I wrapped the affected line in a try/catch block. For two users it

And from the WWDC 2020 10095 Notification video. @objc(stringFromDeviceToken:) public class func stringFromDeviceToken2(deviceToken: Data) -> String { let tokenComponents =

Sometimes we want to get the string value of the device token after requesting push auth from APNS in didRegisterForRemoteNotificationWithDeviceToken. Here’s how you can get that string value in

It looks like there is no public getter for the "window" IBOutlet, even though Interface Builder knows about it and even though there is a public *setter*. You can get to your window by way of the

Say I create a new document-based Mac app in Xcode 12.4. In Document.xib, I see that Document, the File’s Owner, has an outlet “window”. But in the source code of the Document class, if I try

macOS 11.2.1 Some app which shows animated gifs, and which has been working just fine, now is not. @IBOutlet var catImageView: NSImageView! func applicationDidFinishLaunching(_ aNotification:

Sorry, Alex. As usual, publishing this allowed me to see my mistake. First of all, the "msug" thing has to do with the output file, not the input file. Secondly, the problem was in the code -- I was

FYI, you might want to heck out the expected file types in UTTypes.h It’s