Ben, Thanks. You're right. I was getting hung up by thinking that I had to combine the updating of the model and the updating of the UI that displays model elements. But in fact, I can update the

Hey Rick, Pass a reference to the data model to the incoming view controller as it’s initialized for pushing onto the stack. The view controller can then make changes to the model as they happen,

iOS 13+, Xcode 11.4.1, Storyboard-based application. I am using a navigation stack to manage some data edits. That is, • nav-controller root is a list of items. • tap on item to segue to a

I subscribed to this, but I am unable for post to the list. I’m not sure how long they take to activate the account?

Hi, I posted to it, but it doesn’t seem to be working, and not received any mail from it since 2016! Cheers Dave

Hi, I registered for it, but haven’t I haven’t had an acknowledgement? Could you check for me? dave@... Cheers Dave

It's still alive today. -- Shane Stanley <sstanley@...> <www.macosxautomation.com/applescript/apps/>, <latenightsw.com>

And here: https://macscripter.net Bill Cheeseman

Why, there's an AppleScript list right here: https://apple-dev.groups.io/g/applescript —Jens

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