Correction: this is only called once (after loadHTMLString:baseURL:) with navigationType = WKNavigationTypeOther; and also when clicking on a link with scheme ≠ file with navigationType =

Called once; never called when I click on a link.

WKPrivateNavigationDelegate webView:decidePolicyForNavigationAction?

The documentation says: “In apps that run in macOS 10 and later, use the WKWebView class instead of using WebView.” “In apps that run in iOS 8 and later, use the WKWebView class instead of

I would like to build an object similar to a IB "Container View", but which stores a list of contained views and can transition from one to another. Ideally, the view would contain an outlet

I just tried again - and it is working for me too. Probably just a temporary problem. Sorry for the noise. Gerriet.

It’s working for me. I would try logging out, and go in via the link at the bottom of the main developer.apple.com page (which has an extra step).

Logging in to: https://bugreport.apple.com I get a page “Bug Reporter” which does *not* lists my bugs, but just contains one line: “Apple Developer Program Support.”, which is a link to:

On 9/20/2017 5:17 PM, Graham Cox wrote: The docs on -[NSWindow nextEventMatchingMask:untilDate:inMode:dequeue:] says it forwards the message to -[NSApplication

OK, sounds a bit smelly, but whatever works, I guess. The red flag here is the need to “create an event”. I don’t believe there’s ever any reason to do that in mainstream (i.e. app level)

On 9/19/2017 6:43 PM, Graham Cox wrote: Thank you very much. Your code didn't work for me at first, perhaps because of a complication that I did not mention in my original message:

The mouseDragged goes to the view that handled the mouseDown. Since that’s not the same view, you don’t get the mouseDragged. But it’s pretty easy to fix this. On the mouseDown, create and show

I would assume that mouseDragged and mouseUp are sent to the NSResponder object that handled the mouseDown, but I couldn’t find anything documenting that. The other potential problem is that some

In response to a mouse-down event, I want to display an overlay window and have a view in that window process mouseDragged messages. However, it does not get any mouseDragged messages,

I'm trying to use exclusionPaths for the first time and am not having any success. For now, I'm just creating the stuff on the fly in my drawLayer:inContext: method:. The string draws, but doesn't

The compiler probably inlines the call to the comparison function, as opposed to qsort_b which has (of course) already been compiled so it has to make a regular function call. That makes a big

From the man page: The mergesort function is […] intended for sorting data with pre-existing order. Normally, qsort() is faster than mergesort() which is faster than heapsort(). Memory

My guess is that this is not a compiler-related difference, but rather the effect of different algorithms. The performance depends on the initial ordering of the array. My recollection of this subject

I tried this in Xcode Version 8.3.3 (8E3004b) (Swift 3) and: 1. it works: thank you very much. I never would have figured this out from the documentation alone. 2. qsort_b is about 2.25 times slower

Yikes, this is masochistic! This is the prototype: So I think the code looks like this (syntax-checked in Xcode 9 but not tested): The “&sortedArray” relies on the compiler auto-bridging to the