On Fri, 2005-11-25 at 12:06 +0100, Tels wrote: > -----BEGIN PGP SIGNED MESSAGE----- > > Moin Andy, > > On Friday 25 November 2005 11:08, Andy wrote: > > On Fri, 2005-11-25 at 10:54 +0100, Tels wrote: > > > You didn't say which Perl version you are using. Also, have you tried > > > with a non-threading Perl? > > > > I've had this problem on perl 5.8.5 and 5.8.6. I don't think the perl > > version effects it, I think it is some strange interaction between SDL > > and perl. I'm still trying to cook up a reliable test case example > > script. > > Sorry if I sounded rude.
No problems at all, man. That initial message was more to find out if anyone had actually ever tried to use SDL::Timer before and if there were problems, since what I've experienced seems to go beyond any specific installation. > I just asked to try that to corner on the error and maybe find out what > conditions create the problem. It might very well be a low-level problem > in Perl, SDL, threading library (libc/pthreads?) or all of them. Of course. Unfortunately, I find it non-trivial to build a perl and continue to have the one I already installed installed. So it may come to this, but I'd have to build a test system (right now, I'm doing this on my desktop). > > (It would be really nice if you could wait for events with a timeout, > > that would make things a lot simplier without having to eat CPU > > constantly calling poll all the time). > > I agree wholeheartly. Polling is soo 1991 :) It would be cool if SDL::App::loop provided some functionality for a periodic callback, or a way to automatically inject a user-specified event every so often. SDL::App::loop would also be more useful if you could change the %actions hash while it is running. It's really a one-shot-deal. I'm working on this code now (to avoid using SDL::Timer in the meantime) so a patch should be forthcoming. -- Andy <[EMAIL PROTECTED]>
