Space Empires V Editor 1.1 Released

[Devnullicus]

OK, I've put up version 1.1.2, another bugfix release. It has the following changes:

Version 1.1.2

• Added ability to save even if there are errors. Use at your own risk - this COULD corrupt your data!
• Bugfix: When the form warns that your data has errors before saving, it will only show the errors once
• General bugfixes on the parser to make it handle formulas better
• Bugfix: Formula Wizard will reset non-selected vars to 1.0 instead of leaving them at previous value

[President_Elect_Shang]

I sure did, that was the first thing I thought of. I know the entry in the file is correct as I have tested the weapon out and it works as expected. After I hit the Doh! button nothing loads. The exact error I am getting is:

Error(s) reading c:\program files\strategy first\malfador machinations\space empires compilation\se5\gametypes\starfire\Data\Components .txt:
line 509: Unknown key 'Weapon Damage Type'
line 553: Unknown key 'Weapon Damage Type'
line 704: Unknown key 'Weapon Damage Type'
line 749: Unknown key 'Weapon Damage Type'
line 1415: Unknown key 'Weapon Damage Type'
line 1462: Unknown key 'Weapon Damage Type'
line 1512: Unknown key 'Weapon Damage Type'
line 1604: Unknown key 'Weapon Damage Type'
line 1854: Unknown key 'Weapon Damage Type'
line 1898: Unknown key 'Weapon Damage Type'
line 1989: Unknown key 'Weapon Damage Type'
line 2036: Unknown key 'Weapon Damage Type'
line 2085: Unknown key 'Weapon Damage Type'
line 2131: Unknown key 'Weapon Damage Type'
line 2297: Unknown key 'Weapon Damage Type'
line 2383: Unknown key 'Weapon Damage Type'
line 2496: Unknown key 'Weapon Damage Type'
line 2626: Unknown key 'Weapon Damage Type'
line 2673: Unknown key 'Weapon Damage Type'
line 2750: Unknown key 'Weapon Damage Type'
line 2796: Unknown key 'Weapon Damage Type'
line 2849: Unknown key 'Weapon Damage Type'
line 2971: Unknown key 'Weapon Damage Type'
line 3017: Unknown key 'Weapon Damage Type'
line 3120: Unknown key 'Weapon Damage Type'
line 3197: Unknown key 'Weapon Damage Type'
line 3243: Unknown key 'Weapon Damage Type'

And the only change I have made to the file is:

Damage Type Name := Shields Negate
Description := Shields negate all effects of this weapon.
Picture Number := 2
Cannot Penetrate Any Kind Of Shields := FALSE
Cannot Penetrate Any Kind Of Armor := FALSE
Number Of Vehicle Types := 0
Number of Shield Types := 4
Shield Type 1 Name := Normal Shields
Shield Type 1 Penetration Percent := 0
Shield Type 1 Damage Percent := 0
Shield Type 2 Name := Phased Shields
Shield Type 2 Penetration Percent := 0
Shield Type 2 Damage Percent := 0
Shield Type 3 Name := Plasma Shields
Shield Type 3 Penetration Percent := 0
Shield Type 3 Damage Percent := 0
Shield Type 4 Name := Null-Space Shields
Shield Type 4 Penetration Percent := 0
Shield Type 4 Damage Percent := 0
Number of Armor Types := 0
Internal Damage Percent := 100
Facility Damage Percent := 100
Population Amount Killed Per Damage Point := 0.25
Crew Amount Killed Per Damage Point := 0
Is Viral Weapon := FALSE
Number Of Special Effects := 0
Number Of Requirements := 0
Number Of Abilities := 0

I’m sure the formatting won’t hold...

[Devnullicus]

The key "Weapon Damage Type" is actually an invalid key. I think Phoenix-D is correct - you're using an older version of components.txt from before 1.08. The key it's expecting is "Weapon Damage Type Formula".

You should just be able to do a cut-n-paste in your text file and replace "Weapon Damage Type" with "Weapon Damage Type Formula" to get things working.

[President_Elect_Shang]

That was the problem, working now.

[Elsemeravin]

Another very small problem. If I enter a picture number in the component editor, then click on another filed, the picture is not updated. I need to click the 'up' button, then the 'down' to get the right pic to be displayed (I think you should override the "lost focus" event).

But it's getting close to perfection

Something than would be useful for pic selection would be to be able to have the whole pic grid displayed and just have to click on the you want. Currently you have to either know the pic number or click many times to find the right one. If Image Mod arrives, it will only get worse.

EDIT: Another good thing would be to parse teh whole file and indicate on the left column in red the components containing errors. That way you could always be sure you did not insert a new mistyping error without having to click on every single component of the list.

Very good the suggestions when you find an error, can be helpful

[Elsemeravin]

Another problem on the facility editor::
1] I select one facility
2] I modify the pic number by typing 20 in the field
3] I click on another facility
What happens is that the orignal pic number is unchanged but the pic number of the second facility is.

I guess maybe the same for components.

[Kana]

From what little time I've had to look at it...I say great job...also the pic for the main screen is great...

[pujal]

Just curious what file you will be making an editor for next? *cough* vehicleSizes *cough*.

[Shadowstar]

I would like to see a map editor some day, but that sounds like it would require an entirely different kind of program.

[Devnullicus]

Elsemeravin said:
Another very small problem. If I enter a picture number in the component editor, then click on another filed, the picture is not updated. I need to click the 'up' button, then the 'down' to get the right pic to be displayed (I think you should override the "lost focus" event).

Yeah, that's likely what I need to - which also means I probably need to do the same for any editable combobox,
numeric up-down field, etc. I currently do it for textboxes, but it's a pain in the *** because the IDE does not do LostFocus as the defualt event type so I have to go and add it manually in the windows-generated code.

Ah well - it's not a major enough problem that I'm gonna worry about it much, but I'll eventually probably fix it

Something than would be useful for pic selection would be to be able to have the whole pic grid displayed and just have to click on the you want. Currently you have to either know the pic number or click many times to find the right one. If Image Mod arrives, it will only get worse.

Seems like this would be pretty unwieldy once you got to 100+ images, honestly - not to mention memory-intensive (though admittedly, these images are tiny, so that's probably not a worry). A scrollable pane with images that you can click on to choose would probably work. Sounds tedious to work on, though, honestly

EDIT: Another good thing would be to parse the whole file and indicate on the left column in red the components containing errors. That way you could always be sure you did not insert a new mistyping error without having to click on every single component of the list.

The editor already does exactly that on load and when you try to save it. The last column goes red when there's an error. You might have to widen your window to see it though.