Re: How to override properties

> On 2 Oct 2015, at 3:47 pm, Gerriet M. Denkmann wrote: > > So I added @dynamic to the subclass, and all seems to be ok. Maybe. What happens if you pass a ‘someDataClass’ instance to -setStuff:, then return it as type subDataClass? It’s not a subDataClass, but your

Re: Can't get dynamically sized Collection View cells

> On 2 Oct 2015, at 20:30, Peter Tomaselli wrote: > > [re-sending because my last message had size problems] > > Nifty way of demoing there, Roland, I’ll have to try that! > > I’d still be curious to know if anyone is using this feature “in production”. > Because those

Re: Can't get dynamically sized Collection View cells

[re-sending because my last message had size problems] Nifty way of demoing there, Roland, I’ll have to try that! I’d still be curious to know if anyone is using this feature “in production”. Because those crashes, problems rotating (at least for me), and also this, which I definitely ran into

CNCopySupportedInterfaces

I am trying to update some source code which does every second: CNCopySupportedInterfaces and CNCopyCurrentNetworkInfo and extracts the values of kCNNetworkInfoKeySSID and kCNNetworkInfoKeyBSSID. All this is deprecated in iOS 9.0. Xcode 7.0 tells me: 'CNCopySupportedInterfaces' is deprecated:

Re: CNCopySupportedInterfaces

They refused our use, which was to determine if the user has correctly connected to our wifi device, but for some reason the device wasn't responding. Sent from my iPhone > On Oct 2, 2015, at 09:40, Gary L. Wade wrote: > > The original API still works in iOS 9,

Re: CNCopySupportedInterfaces

The original API still works in iOS 9, but to use the new method, you need to ask Apple for an entitlement by sending an email to networkextens...@apple.com. It took me around a week for approval. Be sure to explain your need, especially how simple it is in the scheme of the expectations you

Re: NSView - trouble setting next responder on 10.10 - works okay on 10.9

> On Sep 30, 2015, at 9:15 AM, Jonathan Mitchell > wrote: > > In my app i manage the responder chain on 10.8 and 10.9 to insert the > NSViewController into the responder chain. > The view controllers are inserted just below the NSWindowController so that > designated

Re: questions on WebView for Mac apps

> On Sep 30, 2015, at 11:59 AM, Jens Alfke wrote: > > >> On Sep 30, 2015, at 10:43 AM, Conrad Shultz > > wrote: >> >> WKWebVew is the preferred API. >> >> If WKWebView is missing API that prevents you from

An off-topic question/post that may be worth a short read. (Sorry for the xpost)

As much as I am probably known here for having no filter when I run into problems with Xcode or with my own shortcomings in understanding Cocoa and Xcode, I do this in the interest of getting to a solution and when the solution is found, sharing it. A few years back, I was tasked with training

Re: Implications of disabling ATS?

On Wed, Sep 30, 2015, at 03:45 PM, Mike Abdullah wrote: > > > On 30 Sep 2015, at 17:17, Jens Alfke wrote: > > > > > >> On Sep 30, 2015, at 7:06 AM, Alex Hall wrote: > >> > >> However, before I go doing that, does anyone know of a better way? Are > >>

Re: Implications of disabling ATS?

> On Oct 2, 2015, at 16:01, Kyle Sluder wrote: > > On Wed, Sep 30, 2015, at 03:45 PM, Mike Abdullah wrote: >> >>> On 30 Sep 2015, at 17:17, Jens Alfke wrote: >>> >>> On Sep 30, 2015, at 7:06 AM, Alex Hall wrote:

Re: Implications of disabling ATS?

On Oct 2, 2015, at 2:30 PM, Alex Hall wrote: > > >> On Oct 2, 2015, at 16:01, Kyle Sluder wrote: >> >> On Wed, Sep 30, 2015, at 03:45 PM, Mike Abdullah wrote: >>> On 30 Sep 2015, at 17:17, Jens Alfke wrote: > On

Re: NSView - trouble setting next responder on 10.10 - works okay on 10.9

Hi Conrad > On 2 Oct 2015, at 18:35, Conrad Shultz wrote: > >> >> On Sep 30, 2015, at 9:15 AM, Jonathan Mitchell >> wrote: >> >> In my app i manage the responder chain on 10.8 and 10.9 to insert the >> NSViewController into the responder

Re: NSView - trouble setting next responder on 10.10 - works okay on 10.9

On Oct 2, 2015, at 15:03 , Jonathan Mitchell wrote: > > I am not disputing the veracity of the release notes! When you first posted, I originally suspected (but had no specific knowledge) that the problem was your call to [super setView:] — specifically that this