Jason Tackaberry wrote: > On Tue, 2005-08-02 at 15:53 +0200, Dirk Meyer wrote: >> But maybe mplayer has some problem starting and it takes 2 seconds for >> mplayer to start (maybe nfs problems). Blocking here would block >> freevo. Bad! > > I suppose that's a fair enough argument. But it makes good sense to > have the constructor raise an exception if things aren't in order. Is > there a way to handle exceptions that occur asynchronously with > notifier? I suppose that's really the issue.
I see the problem. But how to you want to raise an exception
asynchronously. Where? In the main loop? Why do you need it? What do
you test in this case? Maybe an exception signal?
| m = Mplayer()
| m.signals['exception'].connect(...)
Dischi
--
The good thing about standards is that there are so many to choose from.
-- Andrew S. Tanenbaum
pgpt3ExcR3S9n.pgp
Description: PGP signature
