CFBundleSupportedPlatforms issue

Hi, On existing project that always built without issue on 10.10/Xcode 6 I am now getting this error with 10.11/Xcode 7: Couldn't find platform family in Info.plist CFBundleSupportedPlatforms or Mach-O LC_VERSION_MIN for myBinary I have 3 pre-complied binaries inside of my project. They do

Re: Mac OSX 10.11 and XCode

> > Yes this was a window server crash. Filed bug report 22943597 with crash log. > > --Richard Charles > This problem seems to be related to having > 1 Graphics Card installed, can anyone verify this? It seems to crash quite often if I am moving from a monitor connected to one card to a moni

Mac OSX 10.11 Log Out/Window Server Crash - FIX!

Hi All, Someone posted this to me: http://la.nvidia.com/download/driverResults.aspx/92183/en It’s application for older Mac Pro’s with NVIDIA Graphics cards - it seems to have done the trick for me, thought I’d share the joy! Cheers Dave smime.p7s Description: S/MIME cryptographic signature

10.11 app crashes in [CIImage createCIImageWithSurfaceBytes:::::]

Hi, when running my app (compiled with Xcode 6.4 against 10.10 SDK) on El Capitan, I get a zillion of these logs along with a ton of graphics glitches: 2015-10-05 15:41:23.084 myApp[2807:50961] +[CIImage createCIImageWithSurfaceBytes:bytesPerRow:x:y:width:height:colorSpace:transform:]: unr

Re: 10.11 app crashes in [CIImage createCIImageWithSurfaceBytes:::::]

Hi, On 05/10/15 15:50, Markus Spoettl wrote: 2015-10-05 15:41:23.084 myApp[2807:50961] +[CIImage createCIImageWithSurfaceBytes:bytesPerRow:x:y:width:height:colorSpace:transform:]: unrecognized selector sent to class 0x7fff742101e0 2015-10-05 15:41:44.560 myApp[2807:50961] CoreAnimation: ignoring

Re: 10.11 app crashes in [CIImage createCIImageWithSurfaceBytes:::::]

On 05/10/15 15:50, Markus Spoettl wrote: Any idea what is going on? I'm running El Capitan in a VMware Fusion 7 that runs on Yosemite, could this be cause of the crash? Turns out it's VMware, the app works fine on a real machine. Sorry for the noise. Regards Markus --

Re: Contained UITableViewController doesn't animate (w/ CoreAnimation) frame change

Anyone? On Oct 1, 2015, at 11:30 AM, Daniel Stenmark mailto:dstenm...@opentable.com>> wrote: I have a rather nested UITableViewController whose AutoLayout height change I’m trying to animate using CoreAnimation. (The final product will have a custom animation timing function, so the UIView an

Re: Value of type '[AnyObject]!' has no member 'Generator'

> On Oct 4, 2015, at 4:53 PM, Graham Cox wrote: > > The explanation as to why Swift doesn’t suck doesn’t fit any notion in > compuer science that I have ever heard of in almost 40 years of programming. https://en.wikipedia.org/wiki/Option_type Optionals (under various names) have been

Re: Mac OSX 10.11 and XCode

That's it. Dave. That's it. My Checkout window still has the nasty cell string overlap, but I can check in to Git from the app without causing a SIGSEV. I disconnected my Thunderbolt display off of my 15" MBP and I was able to commit a file without crashing. I tried 2 installs of 7.0.1 las

Re: Mac OSX 10.11 and XCode

> On 5 Oct 2015, at 20:23, Alex Zavatone wrote: > > That's it. > > Dave. That's it. > > My Checkout window still has the nasty cell string overlap, but I can check > in to Git from the app without causing a SIGSEV. > > I disconnected my Thunderbolt display off of my 15" MBP and I was able

Re: Value of type '[AnyObject]!' has no member 'Generator'

> On Oct 5, 2015, at 1:42 PM, Jens Alfke wrote: > > The problems in this thread seem to stem from missing or incorrect > annotations in one Cocoa class (CIFilter IIRC; I don’t have the whole thread > in front of me.) AVCaptureDevice, actually, but this is exactly it. The problem is that Apple

Re: AVMetadataItem key

This is embarrassing… On 4 Oct 2015, at 5:39 PM, Fritz Anderson wrote: > > func OSTypeFor(code: UInt32, >encoding: UInt = NSMacOSRomanStringEncoding) >throws -> String > { >let codePtr = UnsafeMutablePointer.alloc(1) >codePtr.initializeFrom([code]) >defer { codePtr.destroy()

Re: Value of type '[AnyObject]!' has no member 'Generator'

> On 6 Oct 2015, at 5:42 am, Jens Alfke wrote: > > Optionals (under various names) have been in use in functional languages for > a long time, e.g. Haskell, OCaml, Scala, ML. They’ve been added to Java > recently and are being proposed for C++. > > Optionals are, among other things, a way to

More Swift issues, NSURLComponents

If I import UIKit in here, I get seemingly ridiculous errors: = import Foundation import UIKit if let url = NSURLComponents(string: "http://apple.com/foo/bar?q=123";) { let url2 = url url2.path = nil let url3 = url.copy() url3.p

Re: More Swift issues, NSURLComponents

> On Oct 5, 2015, at 6:03 PM, Rick Mann wrote: > > No errors! But url3 is "let." Why is it allowed here? NSURLComponents is a class, not a struct, so ‘url3’ is a reference, not a value, and ‘let’ just means you can’t reassign ‘url3’ to point to another object. —Jens _

Re: More Swift issues, NSURLComponents

> On Oct 5, 2015, at 18:12 , Jens Alfke wrote: > > NSURLComponents is a class, not a struct, so ‘url3’ is a reference, not a > value, and ‘let’ just means you can’t reassign ‘url3’ to point to another > object. But it wasn't allowed in the copy() case. -- Rick Mann rm...@latencyzero.com

Re: More Swift issues, NSURLComponents

> On Oct 5, 2015, at 8:19 PM, Rick Mann wrote: > >> On Oct 5, 2015, at 18:12 , Jens Alfke > > wrote: >> >> NSURLComponents is a class, not a struct, so ‘url3’ is a reference, not a >> value, and ‘let’ just means you can’t reassign ‘url3’ to point to another >> object

Re: More Swift issues, NSURLComponents

> On Oct 5, 2015, at 18:47 , Charles Srstka wrote: > >> On Oct 5, 2015, at 8:19 PM, Rick Mann wrote: >> >>> On Oct 5, 2015, at 18:12 , Jens Alfke >> > wrote: >>> >>> NSURLComponents is a class, not a struct, so ‘url3’ is a reference, not a >>> value, and ‘let’ just

Re: More Swift issues, NSURLComponents

> On Oct 5, 2015, at 8:59 PM, Rick Mann wrote: > >> On Oct 5, 2015, at 18:47 , Charles Srstka > > wrote: >> >>> On Oct 5, 2015, at 8:19 PM, Rick Mann >> > wrote: >>> On Oct 5, 2015, at 18:12 , Jens Alfke >>>

Re: More Swift issues, NSURLComponents

> On Oct 5, 2015, at 6:59 PM, Rick Mann wrote: > > Huh. I continue to be bothered by the ambiguity/variability of "let"*. Is the > reference immutable or the thing it points to? A variable (var or let) doesn’t “point to” a struct. It _contains_ the struct. I.e. it’s a value, not a reference.

Re: More Swift issues, NSURLComponents

No, no, I get all that. But in practice, these things look and smell the same. Looking at he calling code, you can't tell what's going on. So it has the feel of inconsistency. Especially when a struct can be an AnyObject. Sent from my iPhone > On Oct 5, 2015, at 19:19, Jens Alfke wrote: > >