Re: Re: Is there another way to do performSelectorOnMainThread?

FROM : Michael Ash
DATE : Fri Jun 30 20:46:22 2006

On 6/30/06, Jerry Krinock <<email_removed>> wrote:
> on 06/06/29 8:17, Finlay Dobbie at finlay.<email_removed> wrote:
>
> > NSInvocation is probably even more heavyweight, tbh.
>
> And a real pain!  After using NSInvocation a few times, I realized "Why am I
> putting myself through this torture?"
>
> So, I don't use it NSInvocation or its side-kick NSMethodSignature anymore.
> If I need to invoke a method with non-object arguments, I either rewrite the
> method so it has object wrappers around its arguments, or else wrap it in
> another method that takes only object arguments, then use a
> performSelector:.
>
> My rate of hair loss has decreased, without drugs!


It is almost trivial to write an invocation builder that uses
forwardInvocation: in clever ways, so you could just write:

InvocationBuilder *b = [InvocationBuilder builderWithTarget: target];
[b thisMethod: arg1 goesOn: arg2 theMainThread: arg3];
[[b invocation] performSelectorOnMainThread: @selector( invoke )
withObject: nil];

Of course, once you've done that, it's not much more work to extend it
into a full-blow HOM which would just look like:

[[target performOnMainThread] thisMethod: arg1 goesOn: arg2
theMainThread: arg3];

CHOMP has a performAfterDelay: method which is conceptually very
similar. (Full disclosure: I wrote CHOMP.) Adding a
performOnMainThread method to CHOMP (or indeed another HOM framework)
would be straightforward. Or you can just do it yourself; HOM
implementations are only tricky if you have iteration support.

It's a bit of infrastructure up front to save work later on. Whether
it's better than just writing methods that take dictionaries or
whatever depends on your frame of mind and how often you're doing this
sort of thing.

Mike