On 11.01.2013, at 20:45, Jens Alfke wrote:
> Then you’ll need to block the main thread until the background thread
> finishes its work. You could use an NSConditionLock to do that — main thread
> creates the lock and locks it, passes the lock to the background thread, then
> blocks waiting for
On Jan 11, 2013, at 11:09 AM, Jim Thomason wrote:
> For sake of argument, assume that the work has to be done in an external
> thread, or I have to jump in and out of the main thread some how. I'm not
> actually using URL connections like this in the actual app, I was just hoping
> that it wa
Razafrazin. Okay, you all thwarted my example. :-)
For sake of argument, assume that the work has to be done in an external
thread, or I have to jump in and out of the main thread some how. I'm not
actually using URL connections like this in the actual app, I was just
hoping that it was a nice sim
On Jan 11, 2013, at 8:59 AM, Jim Thomason wrote:
> The issue is that my -doWebStuff:userData:error: method seems to only let
> me write to the pasteboard during the invocation of that method, and once
> it completes I'm done. NSURLConnection is all delegate based, so I wouldn't
> have the result
It's not my app, so it's all opaque to me. I'm trying to implement a
service that sits up in the service menu.
So the user could, for my contrived example, be in Pages, type in their
word, invoke my service, and get the definition automatically pasted into
Pages for them.
I don't have access to a
Can you declare a callback that gets automatically called when the web request
completes, then as a result of this new entry point issues a "needs refresh" to
the GUI item you care about? That GUI item then grabs the data from the source
it's tied to which you have just updated as part of the ca
