Is there a known issue with the value binding being missing from NSButton in Xcode 12?
Here's the Bindings Inspector shown an a fresh NSButton (top image), and shown on an existing button that probably goes back to Xcode 9 or so:
(Hmmm, I can't link to imgur, but you might see an example at their domain plus this top-level path: /a/tElLv9I)
What's worse, when I modify the existing button in most ways, the binding to value breaks completely.
Even more worse, if I delete the binding, close the nib, and re-open it, then there's no way to re-add the value binding to a button that had been already working.
The Cocoa Bindings Documentation indicates that the value binding isn't deprecated and should still be supported.
Did I miss a fundamental breaking change somewhere?
Here's the Bindings Inspector shown an a fresh NSButton (top image), and shown on an existing button that probably goes back to Xcode 9 or so:
(Hmmm, I can't link to imgur, but you might see an example at their domain plus this top-level path: /a/tElLv9I)
What's worse, when I modify the existing button in most ways, the binding to value breaks completely.
Code Block <NSButton 0x7fb233f965d0> valueForUndefinedKey:]: this class is not key value coding-compliant for the key value.
Even more worse, if I delete the binding, close the nib, and re-open it, then there's no way to re-add the value binding to a button that had been already working.
The Cocoa Bindings Documentation indicates that the value binding isn't deprecated and should still be supported.
Did I miss a fundamental breaking change somewhere?
