did anyone notice in components.txt there is double line in the "Tractor Beam II" part
it's something like this
Weapon Display := 14
Weapon Display := 9
now the correct line should be the one with 14, and se4 doesn't seem to mind this.
But my component comparing program kinda hangs when it tries read that part.
I did not know this. Hum, what text compare program are you using, and where can I get it?
__________________
Creator of the Star Trek Mod - AST Mod - 78 Ship Sets - Conquest Mod - Atrocities Star Wars Mod - Galaxy Reborn Mod - and Subterfuge Mod.
quote:Originally posted by Atrocities: I did not know this. Hum, what text compare program are you using, and where can I get it?
well, it's called se4CompCompare and you can only find the Version i'm talking about on my harddisk under the projects folder .
I posted a beta Version of my program in the mod section here http://www.shrapnelgames.com/ubb/For...ML/000019.html , and there is also post here http://www.shrapnelgames.com/ubb/For...ML/002703.html where there is some more info about the program. But the beta Version works fine because it skips the double line...oh and it's not a text compare program but a se4 component compare program...
When you email him, you might remind him that he'd promised to fix this in the 1.35 patch but probaby just forgot. :-)
BTW, if you ever write a techarea compare program, be aware that one techarea has a couple of lines that are out of order--i.e. if all the other techareas have field-a then field-b then this techarea has field-b then field-a. I forget where that is now.
A repeated line is annoying but no big deal. But if you're code assumes that order matters, then the glitch in the techarea file might cause some more severe problems. When the fix didn't come out in the 1.35 patch, I modified my code to assume the field order doesn't matter in my CompHTML and TechView programs.
i sent the e-mail before i read your post raynor, so i didn't remind him.
And about that tech comparing, i think it'll take a while before i start on that, still working on the component comparing...
let's hope that when i start working on it the file is already fixed