Re: performSelectorOnMainThread for a selector with a primitive argument
Re: performSelectorOnMainThread for a selector with a primitive argument
- Subject: Re: performSelectorOnMainThread for a selector with a primitive argument
- From: Eric Crichlow <email@hidden>
- Date: Thu, 16 Feb 2006 12:11:06 -0700
- Thread-topic: performSelectorOnMainThread for a selector with a primitive argument
The thought crossed my mind, but either my understanding of jni
libraries is severely limited (a distinct possibility) or there's no way to
have a class to receive the invocation and redirect to the "real" call. I
think I'm restricted to class methods of AppKit objects.
...Eric...
On 2/16/06 12:06 PM, "Daniel Jalkut" <email@hidden> wrote:
> The safest solution is probably to define a method that takes a non-primitive
> object (e.g. an NSNumber representation of the primitive), and then call
> through to the primitive-arg method.
>
> Daniel
>
> On Feb 16, 2006, at 1:53 PM, Eric Crichlow wrote:
>
>>
>> Problem is, I can't see any way of forcing execution to the main thread
>>
>>
>> other than performSelectorOnMainThread, but that method requires that the
>>
>>
>> invoked selector take an object argument, but there are LOTS of calls that
>>
>>
>> take a primitive type(s) as their argument(s).
>>
>>
>>
>>
>>
>> Is there some solution that I'm completely missing?
>>
>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden