Sparkle during modal dialog in iPhoto

Hm. You've encountered a serious architectural weakness of Sparkle (namely, you can't easily tell it to stop!)

You can use delegate methods to shut down the update, though, when the window is closed.

My main problem is, that I dont control the modality of the window: iPhoto does.

Also I dont think that "stopping" is the problem: I really think, that something with NSURLConnection and the RunLoop is causing the problem. It seems that others have the same problem, when they try to send/receive data when a modal dialog is open (e.g. sending a crashreport). There seems to be some workarounds, and I was hoping that Sparkle already had a solution for the issue...

Any ideas how to tackle the problem?

Maybe it is possible to have Sparkle running in its own thread totally independent of the main thread or the current running runloop. Is there such possibility?

I tried the following:
I create an UpdaterController-Object and call runThread on that in its own thread. In runThread I create an SUUpdater (or subclass) and after creation I let it run in its own runloop in something like the code below:

This works fine but has other problems:
- there is no delegate AFAIK that gets called, when some error happens like host not reachable or something. I see error messages, but the delegate methods are not called
- if an update is available and the Sparkle dialog is shown, then the dialog pops up behind the modal iPhoto exporter dialog and does not react on mouse clicks at all (of course: the exporter dialog is modal...). Also I dont have an handle on the dialog so I could show it modal on top of the export dialog.

So after all I guess that the current Sparkle is not suitable for the environment I am in (iPhoto exporter plugin running while a modal dialog is open) or is there another way (besides extend Sparkle by myself?

It is not possible to run SUUpdater in another thread. It uses UI, which is not thread safe.

It seems indeed that Sparkle is not the way for your purpose. In fact, I think in your situation the only way an updater could ever work is to launch a separate updater app (which, in fact, could use Sparkle).