Thank you. You solved what was turning into a mystery for me.
@AMCerasoli && Desmond Taylor;
Ideally, yes, I was looking to run two timers and wait for the events off each to do their respective updates. It is what I used to do on Allegro 4.2 as the walk around. However, the problem was that Code::Blocks (on Debian64) was not giving me the complete list of options in the pop up box for the ev.timer structure. I was only getting options for .count and .error, which caused me to experiment with trying to obtain which timer was throwing an event by examining this way, which did not look right to start with...
...causing the expected compile error. I did not find anything about this in the docs. My fault, though. Maybe I should have looked in the headers. Soluton found here, third post down on the linked page;
This is a good one too.
Indeed, the suggestion is what I am ultimately after, but let me be sure I am understanding exactly what you mean, first.
My interpretation of your comment. Allow the physics to be updated at the computer's own speed (and get a return of the time_step to divide the physics by) and use the timer only to update the screen(?). The problem is the al_wait_for_event(), before the program will do anything. How can I access the program outside of the wait for event? Threads?
Or am I misunderstanding completely?
For the moment the present solution is great, and what I was looking for. Thanks again.