From: Tucson, AZ
If they are saved into memory once you exit the program your work is gone and everything will have to be resaved next session.
But I thought you wanted to copy existing units within an OOB? Once a unit exists in TOAW, if you exit TOAWxml you can just copy the same unit next time you open the program, why save it as a separate file?
It seems like the only reason for saving it as a file would be if you wanted to use the same unit in different scenarios/gam files, but even then a scenario developer would only need to create the unit one time for each scenario, which seems like it would be much quicker/easier than for me to code this function to save units to file?
Sorry 76mm dude but I can see some utility for saving it as a file also. The idea is to have each separate kind of unit, LCU, aircraft, major naval, etc. so that reading in the appropriate files can create the OOB / TOE of the scenario much faster than doing it by hand. Hopefully, some day the program can read a list of the files that creates the OOB as a file, one for Americans, one for the British, one for the Germans, several for Axis Minors, etc.
Something to consider. Many times an OOB will have many units that are the same. Also some OOBs are very large so to copy a unit and move it up or down in a formation to add it as a new unit can take a bit of time. Why not make it possible to copy a unit and save it in a file so that when another unit of that type is needed it can be selected from the file where it was saved and simply added to the OOB. In a very large OOB this can save a bunch of time. It could be added by selecting a unit currently in the OOB and adding it so it comes before the selected unit.
< Message edited by larryfulkerson -- 2/2/2019 2:27:57 PM >
I seem to have been only like a boy playing on the seashore, and diverting myself in now and then finding a smoother pebble or a prettier shell than ordinary, whilst the great ocean of truth lay all undiscovered before me. - Isaac Newton