e sure".
And I indicated it failed in a playground. It did build successfully in a
command line project, though.
--
Daniel Blakemore
Pixio Software
On Thu, Dec 11, 2014 at 5:22 PM, Marco S Hyman wrote:
>
> > Why did it compile if it's an incomplete type? Shouldn't that
;.
I appreciate the quick help. =D
--
Daniel Blakemore
Pixio Software
On Thu, Dec 11, 2014 at 4:59 PM, Marco S Hyman wrote:
> On Dec 11, 2014, at 3:24 PM, Daniel Blakemore
> wrote:
> >
> > If I do this, however, it breaks:
> > var arr2 = [Array](count:6, repeatedValue:[
uot;
struct Color {
var r : Float = 0
var g : Float = 0
var b : Float = 0
}
var arr1 = [Array](count:6, repeatedValue:[Int](count:8,
repeatedValue:Int()))
var arr2 = [Array](count:6, repeatedValue:[Color](count:8,
repeatedValue:Color()))
Any insight would be appreciated.
--
D
that Swift is the new C, but it does have some issues
that need to be worked out/around or at least explained before I move over.
--
Daniel Blakemore
Pixio Software
On Fri, Nov 21, 2014 at 7:24 PM, Quincey Morris <
quinceymor...@rivergatesoftware.com> wrote:
> On Nov 21, 2014, at 17
your view is
initialized with a zero frame: until they make it hard to see useful logs.
Roland seems to feel the same way.
At the end of the day, though, your issue appears to be entirely contained
within Apple code, so I'd ignore them and chalk it up to another slight
lapse in QC recently.
a method set up specifically to be called by the
system. It triggers the same mental red flags as calling layoutSubviews
(rather than layoutIfNeeded) or something else that is reserved for the
system to call.
Thanks for the feedback.
--
Daniel Blakemore
Pixio Software
On Wed, Oct 15, 2014 at 10:12
eCameFromATouch.
The irksome thing is that it used to work and now doesn't and there's no
API diff around selectedSegment and the wording in the documentation didn't
change between iOS 7 and 8.
So I don't know if it's an intentional decision or an oversight.
--
Daniel Blakem
ves my app in an inconsistent state.
For reference, see this example project
https://github.com/danblakemore/SegmentedNope.
This worked in iOS 7. It now does not. What has changed?
--
Daniel Blakemore
Pixio Software
___
Cocoa-dev mailing list
it had copy-pasted Objective-C in it that was clearly not correct [which
required me to restart my entire computer]).
What am I doing wrong that I need to do right?
--
Daniel Blakemore
Pixio Software
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
t on this? Has anyone else tried to use viewWillTransition... in
a photo extension specifically (Googling indicates that it may work in
other extension types, such as Today)?
--
Daniel Blakemore
Pixio Software
___
Cocoa-dev mailing list (Cocoa-dev@lists.app
I'll do that. I had meant to post here with a less involved
explanation/project, but when it was all said and done, I guess it came
together well enough to be easy to bug report.
--
Daniel Blakemore
Pixio Software
___
Cocoa-dev mailing list (Coco
(and hopefully to someone at Apple ;-] ).
As such, I created a new project from the ground up with a (mostly) minimal
setup to reproduce the bug under the conditions that I saw it (multiple
view controllers).
That project can be found here:
https://github.com/danblakemore/QuantumEntanglement
12 matches
Mail list logo
