On Dec 20, 2016, at 15:32:18, Alex Zavatone wrote:
>
> po NSStringFromSelector(action)
> expr (void)NSLog(@"%@", NSStringFromSelector(action))
Does action have a parameter (such as "(id)sender")? If so, then the name is
"action:", not "action".
--
Steve Mills
Drummer, Mac geek
I'm in the middle of lovely iOS non ARC code of a few (6) projects which are
occasionally optimized out of the debugger's JIT.
Additionally, every screen is built from XML files so, it's a little hard to
trace which button causes which action to go where.
This makes life less fun than it
I’ll also argue that if you’re needing to do this kind of thing from a
background thread, your code isn’t factored properly.
Managing the UI of the app is far too complex a task to try to coordinate among
multiple threads. The current best practices for concurrent programming suggest
that you
On Tue, Dec 20, 2016, at 08:59 AM, Andreas Falkenhahn wrote:
> So everybody knows that all things relating to UIKit have to be done
> on the main thread.
>
> But what about AVFoundation functions which bear some resemblance to
> UIKit APIs? Do these have to be called on the main thread too or can
So everybody knows that all things relating to UIKit have to be done
on the main thread.
But what about AVFoundation functions which bear some resemblance to
UIKit APIs? Do these have to be called on the main thread too or can
they also be called from a worker thread?
For example, when adding an