ATTN: Gimboid about Component editor

[Nebraskan]

Gimboid,
I had a bad experience with you component editor yesterday. I used it to put a new component into the DGold mod and when I tried to play SE4 with the DGold mod it came up with errors in the component.txt files. I think this came from moving the component up from the bottom of the list, where a new component starts, up to where the similar components were. The error I got was a non weapon component having some entries other than none for weapon attributes.

I am not exactly sure what the errors were as I fixed them and deleted Component Editor, I over-reacted and was ticked off. I need to work on that. Other than that I think Component Editor is a great idea, just needs a little more work.

[Gimboid]

Nebraskan,

I just attempted to repeat the error you mentioned by moving a non weapons component around the component list. I moved it up and down and used all the possible movement buttons, to no avail.

I was not able to make it screw up the weapon attributes for the non-weapon i was moving around(or for any other weapon or non-weapon component on the list).

Were you using the latest Version?, because i have tweaked a few things since previous iterations. The latest Version is in my sig below (0.82)

If its at all possible, could you download the latest Version and see if you could repeat the error and if you can, post here or email me the snippet of the components.txt file that is messed up and details about the steps taken in order for the program to mess up the data. That way i can squash this bug, if i havent already (if you were using an older Version that is)

I can understand your frustration, after having worked away at a mod only to have some of the data become corrupt i do not want my program to cause any such errors so i would like to fix any anomolies that come up.

Cheers

[Gimboid]

Actually, ive just done a further update. The latest Version is now 0.83...

With the latest Version when you copy a component it is now inserted immediately after the component that was copied, thus negating the hassle of moving the component from the bottom of the list to be in the same vicinity as the component that it was copied from.

Also - having thought further about your situation i can recall that in earlier Versions of my program the copy button was not working correctly. And the error it caused was to mess up the data fields for the weapon attributes just as you mentioned (whether the component was meant to be a weapon or not).

That would seem to be to be the most likely cause of the error, and then the corrupted data fields were moved around the list when you adjusted the components position with the movement buttons. The movement buttons would not have been responsible in that case.

If i am right and you were using an earlier Version then it could be solved as i mentioned earlier, by updating to the latest Version (0.83) which does have the copy feature working correctly

[Nebraskan]

Gimboid,
Yes it is an older Version 0.71 to be exact.

I will d/l 0.83 and give it a try and let you know.

Thanks