Re: [Woodchuck-devel] [gpodder-devel] Closing gPodder after a Woodchuck-triggered update

[Neal H. Walfield]

I find it slightly annoying that I have to close gPodder every
morning, because overnight Woodchuck triggered an update.

Yesterday, I thought of a simple solution, which should work most of
the time:

 - When Woodchuck starts, check if the user is idle
   - If so, start monitoring the user's activity.
 - After all Woodchuck-triggered updates complete, check whether 
   the user has remained idle the whole time.
   - If so, quit.

Since Woodchuck prefers to start transfers when the user is idle, this
should work much of the time.

This could be mostly realized in gPodder's Woodchuck plugin, however,
the plugin needs a way to trigger a clean shutdown.

What do you think?

Thanks,

Neal