performSelectorOnMainThread for a selector with a primitive argument
performSelectorOnMainThread for a selector with a primitive argument
- Subject: performSelectorOnMainThread for a selector with a primitive argument
- From: Eric Crichlow <email@hidden>
- Date: Thu, 16 Feb 2006 11:53:14 -0700
- Thread-topic: performSelectorOnMainThread for a selector with a primitive argument
Can I do it???
It seems to me like it would be a fairly common usage, but I can't find any
reference to it.
I maintain a jni library for our Java programmers. Some things they need to
do require making AppKit UI calls. Lots/most/all? AppKit calls aren't thread
safe. I'm guessing that maybe some mysterious crashes we're having, even in
supposedly single threaded Java apps, that seem to occur around calls to the
jni library, are related to threading. So, just to be sure, I want to make
sure I force all of the AppKit calls in the library to occur in the main
thread.
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?
...Thanx...
...Eric...
_______________________________________________
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