That's pretty awesome!
On Fri, Oct 2, 2015 at 1:01 PM, Alex Zavatone wrote:
> As much as I am probably known here for having no filter when I run into
> problems with Xcode or with my own shortcomings in understanding Cocoa and
> Xcode, I do this in the interest of getting to a solution and when
> On 4 Oct 2015, at 11:10 pm, Roland King wrote:
>
>> A) Ah, so it's Swift continuing to suck.
>
> No, not at all, Swift is being consistently consistent. The variable is a
> ‘!!’ which means it’s implicitly unwrapped optional of an implicitly
> unwrapped optional of an array, so when you use
On Oct 1, 2015, at 3:59 PM, Jan E. Schotsman wrote:
>
> Sorry for this stupid question but I just don't know how to do this.
>
> I have an AVMetaDataItem with
> key = protocol? Int32(1851878757)
> as shown by the debugger
>
> How can can extract the value 1851878757 which is the four char code
> On Oct 4, 2015, at 09:51 , Quincey Morris
> wrote:
>
> On Oct 4, 2015, at 05:10 , Roland King wrote:
>>
>> Quincey sharpens his keyboard
>
> No, the only person who’d get hurt is me.
>
> There are actually several strange things going on here in the
> AVCaptureDevice API, and they look l
On Oct 4, 2015, at 05:10 , Roland King wrote:
>
> Quincey sharpens his keyboard
No, the only person who’d get hurt is me.
There are actually several strange things going on here in the AVCaptureDevice
API, and they look like bugs to me:
— ‘devices’ and ‘formats’ are documented to return array
> On 4 Oct 2015, at 18:56, Rick Mann wrote:
>
>
>> On Oct 3, 2015, at 23:03 , Roland King wrote:
>>
>> Apply the usual swift technique and break it down into more than one line
>> then go look at the types of each variable.
>>
>> let ff = device.formats
>> let pp = ff!
>>
>> option-click
> On Oct 3, 2015, at 23:03 , Roland King wrote:
>
> Apply the usual swift technique and break it down into more than one line
> then go look at the types of each variable.
>
> let ff = device.formats
> let pp = ff!
>
> option-click on each of those variables and you’ll quickly see the ‘!!’ o
> On 3 Oct 2015, at 18:43, Quincey Morris
> wrote:
>
>
> I suggest you consider breaking your view controllers apart into two objects.
> One, a “view responder” would be a NSResponder subclass that you insert into
> the responder chain just below the window controller. The other, an actual
