Re: [Alephmodular-devel] Detangling/de-Mac-ifying

[Timothy C. <da...@ma...>]

Agh...I forgot about that, too...Br'fin, can you fix this list's  
reply-to address, by chance?

On May 17, 2005, at 6:02 PM, Br'fin wrote:

> I was going through and removing direct calls to Mac-specific  
> things. At the heart of the program is an event loop. Figure out  
> what the user is doing to the computer, then have the computer  
> update the state of the game-world. And finally display the result  
> on the screen with sound.
>
> In the case of AM, this is, I believe, in shell.cpp. However, as a  
> further snarl. I don't think going with a straight up abstraction,  
> like I did with some other areas of the code, necessarily gets what  
> we need out of it. The process of updating the state of the world  
> and rendering it happens in this event loop. So I want to add a  
> thread in here. But I don't know enough about threads to get my  
> brain too well around them either.
>

Well, I know something about threads in theory...is the problem  
you're having with your brain not wrapping more in concept, or code?   
'Cause I'm sure I can help with the former, while the latter might be  
more difficult.

I've been looking a bit at the code so far, and I've been able to  
understand pretty much all of it...haven't really gotten into the  
main event loop part yet; I'm just working my way through  
marathon2.cpp and shell.cpp and seeing what I can see.

Timothy Collett

--

"We are the Rangers. We walk in the dark places others fear to enter.  
We stand on the bridge, and none may pass. We live for the One. We  
die for the One!"