Hi, I see that the old AppleScript list that was hosted by Apple is no more, does anyone know of an alternative? Thanks a lot Dave

Of course, as soon as I sent the message, I figured out a way to do the debugging, by setting the optimisation level for the debug version. So now I can see where the problem is, sort of. It's weird.

One thing I forgot is if you are debugging a release version (I expect that this is a Mac app), you may want to make sure that you are not stripping debug symbols.

Report the properties of the URL beforehand. At one case, I even had my old reporter get the properties, put them in a string and mail them to a specific email account to see what was going on. You

I am getting a crash, but only in the release version. I get a very helpful "Error 1" if I try to debug the release version, and logging doesn't get me anything, as the crash prevents the log entry

Hi Graham, I have just encountered this exact same issue, and indeed, keeping a copy around of my window solved the issue. The approach that I took was a little different though and did not require me

You've also removed support for Unix line endings. Now it only supports Windows line endings; probably a bad idea. I'm mystified too, but IMHO enumerateLines is a better way to do it. —Jens

Ok, I still don’t understand what’s going on, but I’ve got an alternative solution. (Maybe somebody can clarify this for me??) WHAT DOESN’T WORK IN MY CONTEXT: do { var str = try

Hi Kurt, re-reading the documentation on basic event handling might help: EventArchitecture.html particularly “The Path of Key Events”, and “Handling Key Equivalents" Note that I mentioned

Oh. Yeah. That’s too much work. var str = try String(contentsOf: urlContext.url) // (1) let lines = str.split(separator: “\r\n”) // (3) works and is faster in that you’ve removed an

Doesn't Swift's String class have higher-level methods to break a string by lines? NSString certainly did. —Jens

Are the lines terminated with a carriage return/line feed pair or are they terminated with the character string "\r\n”. The results of step 2 and 3 are what I’d expect if the string contained the

Can you take a look at this for me? I think I’ve been cooped up at home too long, because whatever is going on, I’m missing it. Context: I’m working on a data import function for a new app. It

macOS 15.4 I have a SwiftUI ContentView, which contains a few vertically stacked Views. For one of these I need the following functionality: when the mouse moves inside the view, or when the view

Hi Sandor, from the stacks it looks like you’ve Finder Extensions installed on your system. Can you disable / uninstall them and verify if the issue is still reproducible? Best, Rafał

Thanks Sak, My discovery seemed random and unsettling, so I kept digging. I will read the docs you’re referring to But a sheet does seem to do the trick. What’s weird is this code has worked for

No, I have a non-sandboxed app and it works fine. I think the problem is that you are using NSSavePanel:runModal. If you look in the doc'n, it says: "This method invokes NSApplication's

Already reading app sandbox design guide, was hoping for pointers to other apple resources, videos, etc… Thanks, Sandor

Took a guess and enabled sandbox and added read/write to user selected file and the hang went away. Is it true that I cannot make an unsandboxed app and uses the NSSavePanel? I know this is a data

Ran into an interesting issue today… Mac app Xcode 9.4.1, 32bit, 10.12 SDK, 10.6 Deployment Target non-sandboxed app I am opening an NSSavePanel to allow a user to save the