Cocoa Auto Layout Warning in Xcode console

2015-08-19 Thread JanakiRam Palepu
Hi All, I'm receiving the following message in Xcode console log whenever i launch my window. 2015-08-19 21:34:07.352 GDV[36081:1272774] Layout still needs update after calling -[NSScrollView layout]. NSScrollView or one of its superclasses may have overridden -layout without calling super.

Re: Cocoa Auto Layout Warning in Xcode console

2015-08-19 Thread Graham Cox
This is emitted by both the Font Panel and the Save/Open panel. It’s an Apple bug, seems like they add warnings in one parrt of the system but then ignore it in others. —Graham On 20 Aug 2015, at 2:07 am, JanakiRam Palepu palepujanaki...@gmail.com wrote: Hi All, I'm receiving the

Button Image Behavior

2015-08-19 Thread James Cicenia
Hello - I am trying to toggle a button with three states. In IB I have it set to “off” In the code I toggle as such: func toggleStatus() { if(product.favorite == false product.avoid == false){ product.favorite = true product.avoid = false

Swift: 'If' statement needing parentheses on closure return value property access?

2015-08-19 Thread Antonio Nunes
In Swift 2.0 I can write this: repeat { … } while reminder.exclusions.filter { $0.spansTime(t) }.count 0 but I can’t write this: if reminder.exclusions.filter { $0.spansTime(t) }.count 0 { … } which gives an error

Re: Swift: 'If' statement needing parentheses on closure return value property access?

2015-08-19 Thread dangerwillrobinsondanger
Maybe file a bug to see if it's expected. But at first glance it seems clear to be ambiguous scope. it can't figure out that the first {} is part of the condition rather than the thing triggered by the condition. A do while knows more easily because the {} after do is what is conditionally

Re: Swift: 'If' statement needing parentheses on closure return value property access?

2015-08-19 Thread Quincey Morris
Clearly it’s a “more ambiguous” context than the while case, which prevents the compiler from realizing that there is an alternative analysis that works. In that case, it’s the error message that’s at fault, since it doesn’t really tell you what’s wrong. In fact, this “consecutive statements”