Questions: 1. Do you get different sizing behavior for the same image depending on which case/path gets taken? 2. How does the UIImageView size compare with image.size for the misbehaving case?

I have a UIImageView, which I load with the following function: func loadData() { guard let recipe = recipe, let fileN = recipe.photo, !fileN.isEmpty else { imageView.image = nil

I have a little app that writes alias files to its App Support folder on a regular basis. The app is sandboxed, so that ends up in ~/Library/Containers/<apputi>/Data/Library/Application

I did. The error message is: Cannot find service provider for selector nnn:userData:error: or nnn:: for service nnn Which suggest that two selectors are indeed tried. That is: Objective-C uses the

This doesn’t look right, and I don’t know why it works. If you put the name “nnn” in the info.plist, the selector it looks up should be “nnn:userData:error:”. The Swift 4 function

Now this is ok: @objc func nnn(_ pboard: NSPasteboard, _ userData: String) Where nnn = value of “Instance Method name” from Info.plist I am sure this is very well documented somewhere. The

This does work: @objc public func abc() { print(#function) } Well, it did, but hidden somewhere in DerivedData/… Now it works. Sorry for the noise. Gerriet

I have a Swift project called TestSwift: import Cocoa @NSApplicationMain class AppDelegate: NSObject, NSApplicationDelegate { @IBOutlet weak var window: NSWindow! func

This works: - (void)lookUppString:(NSPasteboard *)pboard userData:(NSString *)data error:(NSString * _Nullable *)error { NSLog(@“%s",__FUNCTION__); } But this does not: func lookUppString(_

Well, things get more complicated when you use non-Obj-C types, but it’s not necessarily true that you can’t use Swift types. In the case of the model, it may be sufficient that your “model"

Thank you, You are spot on with explaining the problem and I understand your answer and concerns. Sending up a NotificationCenter rocket in read(from:ofType:) confirms your explanation. Unless I’m

Well, you’re Doing It Wrong™, but it’s not entirely your fault. This is one of NSDocument’s big messes that we’ve been stuck with for the last 10 years or so. What’s actually going wrong

Firstly I’ve uploaded a very cut down project which shows the problem. https://www.ilike.co.nz/downloads/testDocument.zip "Propagate the data reversion to your window controller and view

Propagate the data reversion to your window controller and view controllers can be difficult, because any setup you did in windowDidLoad/viewDidLoad is not automatically redone. It can be especially

I've been trying track the correct path from document to Control and back again. Document automatically loads WindowController.document I use didSet to loop down the ViewControllers and set there

macOS 13.5 I made a WkWebView and added navigationDelegate and uiDelegate and implemented (almost) all delegate methods, each containing a print(). 1. I never see any prints (running in Xcode) 2.

You can do something like this: It’s settable from within its class or struct, but not from outside, which is as close as you can get to ‘lazy let’ AFAIK.

This works: lazy var session = makeSession() func makeSession() -> URLSession { let sessionConfig = URLSessionConfiguration.ephemeral return URLSession( configuration: sessionConfig ) } First: is

AFAIK, there are no documented limits and I believe you aren’t subject to a number of same-origin policies, but this is Apple so who knows. Anyway, you inject JavaScripts using a

If the web-page I am interested in is *not* under my control, could I still "write the DOM stuff in JavaScript” ? If so: how would I start doing this? Currently I am doing stuff like: get