Jason Tackaberry wrote: > On Thu, 2007-12-27 at 20:29 +0100, Dirk Meyer wrote: >> reason why kaa.notifier is in kaa.base. There is only one small patch >> in our pynotifier that is not in the real pynotifier and that is for >> running our mainloop in a different mainloop as thread. So if you have >> apps using pynotifier, you can merge them. If you don't, you do not >> need pynotifier. > > Is this actually a patch to pynotifier or just functionality over top of > it? If it's a patch is there any way we could get it merged upstream? > Or if it's too specific, generalize it enough to make it mergeable?
It is the simulate parameter for nf_generic. We need it to run the notifier loop in a thread for testing. This is a very kaa specific patch crunchy does not like in pyNotifier. Dischi -- This message was sent to you via email in much the same way bricks aren't.
pgp7OS6m9gWwD.pgp
Description: PGP signature
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ Freevo-devel mailing list Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel
