so sue me
I know this is other places, but ive still never seen a comprehensive guide to picts and descs. Some are listed in the bible, but some arent.
What are...?: reserved picts for interface/etc. Recommended IDs for picts used for shans and such. Reserved Desc IDs, and recommended range for the texts other than onaccept for missions (which i know is predetermined).
What are the pixel dimensions for many things, like the targeting image, or main menu. I used the viper betting buttons as a target pick for a miniplug (since those buttons are some of the few pics included in absolute minimum, and it looked fitting). If memory serves, the picture showed up fine in the outer menu, but was squished on my hud. A better documentation of this behaviour would be cool. Also, I saw rumor somewhere of a bar pic, something about the size of the news pick (probably half the height) That shows above the bar description. Its pixel dimension is especially important, since its unused in the stock scenario.
Also, could someone sketch out what all of the fields in the colr rescource do? Something about the meaninglessness of words like 'main menu' and rollover animation, sliding buttons, etc confuses me. Its just not terribly clear. Things like I remember the game crashed when you gave it a number of picts in the button animations to different from the default version, even something sick like it needing an odd number of frames, but im totally talking out of my ass. I do remember something like that though. In any case, colr looks in need of a guide (wink wink ZP, you done great. Work thine magic here). Crap also like that the animation at the top isnt looped, its random (though i obviously know that part).
Is intf beavior well understood either? Like nonsquare radar, or really really big radar, or if you can make a bigger slot for targeting pics, etc. Also, what is the generally accepted choice of fonts? I bet the answer is no, but can the bar be somewhere other than the right edge?
Im not particularly lazy, I just feel I'll better serve the community testing stuff we dont already understand. If there is any part that is not already adequately tested and retested, ill set up a little guide on it myself.
This post has been edited by NebuchadnezzaR : 09 May 2005 - 10:35 AM