Re: [AD] Strange timer behavior in 5.2.1.1

[<trent@xxxxxxxxxx>]

I think the examples used to be built as console applications. I’m not sure why they are now built as Windows apps but maybe somebody knows.

 

 

 

From: Edgar Reynaldo
Sent: August 21, 2016 2:47 PM
To: trent@xxxxxxxxxx
Cc: Allegro Developers
Subject: Re: [AD] Strange timer behavior in 5.2.1.1

 

 

On 8/21/2016 3:41 PM, trent@xxxxxxxxxxx wrote:

Thanks for reporting this. Looks like I messed this up. I think this patch will fix it:

 

diff --git a/src/timernu.c b/src/timernu.c

index 9179969..66f1c33 100644

--- a/src/timernu.c

+++ b/src/timernu.c

@@ -104,6 +104,7 @@ static void timer_thread_proc(_AL_THREAD *self, void *unused)

       al_lock_mutex(timers_mutex);

       while (_al_vector_size(&active_timers) == 0 && !destroy_thread) {

          al_wait_cond(timer_cond, timers_mutex);

+         old_time = al_get_time();

       }

       al_unlock_mutex(timers_mutex);

 

 

Can you try this in the PacMan game? Ex_timer_pause won’t work unless you build it as a console app (the examples are now built as Windows applications), but I confirmed it works on Linux.

 

I'll rebuild the debug dll and have Neil test it out. Thanks for the prompt reply.

So what to do about ex_timer_pause? Is there an easy way to rebuild the library examples as console apps to test this? Besides just compiling it myself? I'm using MinGW 5.3.0 (and 4.8.1).

Edgar