> On 15 Oct 2016, at 5:08 PM, Gerriet M. Denkmann wrote:
>
> Any workaround for these multiple (and unnecessary) calls?
Do they actually cause any problems? If not, just move on - there’s probably no
point worrying about it. If they do cause a problem, then that might indicate a
code smell o
> On 2016 Oct 14, at 23:08, Gerriet M. Denkmann wrote:
>
> My app (macOS 12) observes a value in NSUserDefaults. Starting with macOS 12
> observeValueForKeyPath:… is called at the start of the program, although
> nothing has changed yet. When the value actually changes, it is called twice.
I am not an expert on Interface Builder, so I hope to learn something about how
IB simulates the display of views or how IB defined views are constructed at
run time.
I have a UI that includes textured rounded buttons with text labels. In IB,
when the IB window is inactive, the buttons display
> On Oct 17, 2016, at 11:35 AM, Raglan T. Tiger wrote:
>
> void x::Clear(apointList &list)
> {
>if ( ! &list )
>return;
> }
It’s not valid for a C++ reference value to refer to null. So the optimizer is
allowed to assume that `&list` is a non-null pointer, and the test in the `
Moving , finally, to Xcode 7.3.1, I get a weird bug.
If I build a release configuration with the recommended optimization level
(fastest, smallest) then this code
void x::Clear(apointList &list)
{
if ( ! &list )
return;
}
never returns when apointlis &list = 0x as sh
