On Jun 4, 2014, at 10:04 PM, sonofsky2...@gmail.com wrote:
> Does anyone know weather an iPhone5 can be a USB Host Device?
No.
--
Scott Ribe
scott_r...@elevated-dev.com
http://www.elevated-dev.com/
(303) 722-0567 voice
___
Cocoa-dev mailing list
Hi all,
Does anyone know weather an iPhone5 can be a USB Host Device? I have a USB
Slave device, I want to connect this device to iPhone5. I will apply a MFI
Licensees.
Best regards,
Sunny
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Ple
On 5 Jun 2014, at 12:54 pm, Lee Ann Rucker wrote:
> It does? When I saw your subject line I thought you were were talking about
> SourceView style, because I have one - it's view-based - and I'd been
> wondering if it was possible to get a unified multi-selection gradient.
Actually I see dif
On Jun 4, 2014, at 7:05 PM, Graham Cox wrote:
> I have a view-based NSOutlineView, in which I'm using a custom NSTableRowView
> subclass to customise the appearance of the selection. This works fine.
>
> However, because I'm using a gradient effect for the highlight, when there
> are several c
I have a view-based NSOutlineView, in which I'm using a custom NSTableRowView
subclass to customise the appearance of the selection. This works fine.
However, because I'm using a gradient effect for the highlight, when there are
several contiguous rows selected, each row draws a separate gradien
Sweet. Thanks guys.
That's exactly what I needed to frame why this is bad to our former dot net guy.
Cheers.
On Jun 4, 2014, at 6:02 PM, Quincey Morris wrote:
> On Jun 4, 2014, at 14:45 , Alex Zavatone wrote:
>
>> But I need to come up with an explanation of explain why that is a bad idea
>
On Jun 4, 2014, at 14:45 , Alex Zavatone wrote:
> But I need to come up with an explanation of explain why that is a bad idea
> and why it smells
It smells because a computationally intensive while loop will stall the
dispatch queue that’s stuck on it.
If you’re programming with *threads*, it
On Jun 4, 2014, at 4:26 PM, Alex Zavatone wrote:
> On Jun 4, 2014, at 4:07 PM, Ken Thomases wrote:
>
>> You have a misconception as illustrated in the above quotes. I think you
>> think of ARC as a garbage collector that needs idle time or for execution to
>> return to the frameworks in order
On Jun 4, 2014, at 4:02 PM, Quincey Morris wrote:
> I think the deeper problem is that a while loop of this kind in an
> asynchronously executed block is a bit of a code smell.
Exactly.
But I need to come up with an explanation of explain why that is a bad idea and
why it smells. I know it
On Jun 4, 2014, at 4:07 PM, Ken Thomases wrote:
> On Jun 4, 2014, at 2:24 PM, Alex Zavatone wrote:
>
>> As it turned out, my coworker had created a dispatch_async thread to start
>> processing the video and within it, started at a framecount of 0,
>> incremented it within a while(true) loop an
On Jun 4, 2014, at 2:24 PM, Alex Zavatone wrote:
> As it turned out, my coworker had created a dispatch_async thread to start
> processing the video and within it, started at a framecount of 0, incremented
> it within a while(true) loop and grabbed the frame every time there was a new
> framePi
On Jun 4, 2014, at 12:24 , Alex Zavatone wrote:
> His response was "Well, I was able to autorelease any offending bits within
> the loop without a problem, what's the big deal?"
I think the deeper problem is that a while loop of this kind in an
asynchronously executed block is a bit of a code
I was just reviewing a team member's code on iOS 7 for reading the
CVPixelBuffer from a video frame, storing it in a UIImage and converting to
grayscale.
Was testing against 720p video in the iPad and was pretty surprised to see
memory leak faster than I've ever seen before, but only after o
Hi,
Yes, the documentation is wrong or confusing at best, I’ve tried it, it doesn’t
work. I think it’s meant for a number of operations that need to wait for the
preceding operation to complete before the next one continues.
I also wondered if the NSOperation “waitUntilFinished” method might wo
14 matches
Mail list logo
