Re: [Alephmodular-devel] Display Abstraction Landed?

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

 >Well, the replays are solid in terms of sync. But if something changes  
>then the replay is off. And classic OOS errors seem to come from  
>someone's emulation getting off for some unclear reason.

You know, I seem to remember something Woody was doing a while ago, while chasing down OOS problems in A1.  Didn't he find some actual errors in the RNG code, that could, at least in theory, lead to OOS?

Yeah, this past January 12 on marathon-devel, he said he thought it was a problem with Marathon's min() function.  Maybe you should look into that?

>The only resource we save into files currently is a map preview in the  
>saved game that is supposed to show up in Open/Save dialogs and the  
>finder. What's annoying is this worked fine in OS X 1.0, but under 1.1,  
>Nav Services still created the preview, but the finder ignored it for  
>me :/

Yeah, I remember that.  I wonder why it did that?  Very annoying.  Maybe Panther will fix it?

>That preview is currently stored in a very platform specific way,  
>supposedly so that that platform can and should show it elsewhere :/

In theory, that sounds good.  

>The Real modularization part is yet to come... I should dig up one of  
>the roadmaps and probably check into into the documentation directory.

That's kind of what I thought.

>> A rough order might be
>>         Modularizing basic file capabilities
>>         Modularizing basic display capabilities
>>         Modularizing sound handling
>>         Modularizing preferences
>>         Modularizing gui
>>         Modularizing game elements
>>         Modularizing networking

Do you have any idea, at this point, what will be required a) as prerequisite for these, and b) to actually do them?

Just curious.

Timothy Collett

He who asks is a fool for five minues. He who doesn't ask is a fool forever.