I'll update the tut when I get the time. all this thing about threads it's incredible.
I have uploaded the weapon_S tut.
Why are you using those // and _ _ like if you were writting on allegro.cc? On the Wiki that doesn't work.
ok we have some questions:
1 - A thread is like a program running separately. Separately means you have no idea how far it has run, and neither do they know about each others globals?.
2 -thread_1 is allocated. Don't forget to deallocate it afterwards. Shouldn't you check
it's its value?
Neither al_start_thread and al_create_thread returns a value so how could I check it?
3 - The thread will be running the function Func_thread and getting the pointer *data as its argument when it starts. (Or only after it started it head hurts)
To be honest I don't understand the question.
4 - al_wait_cond takes a locked mutex as an argument???
On entering this function, mutex must be locked by the calling thread. The function will atomically release mutex and block on cond. That is what the manual says, I don't know if you was referring to another thing.
5 - In what order are you discussing the file? In what order was I discussing the file? I already discussed this???
When I said "Everything until here should be already clear" I was referring to the rest of the code the initialization of allegro, mouse etc, I guess I can remove it, though.
Instead of a while can't we use an if?
tags shows the letters too small, can't be increased?