Update:
Everything loads just fine now, time for coding the saving
Comments?
Main screen:
Click on [...] next to teamtype#1 or 2 to call up this TeamType Editor screen:
Those two small buttons next to IDs are 'clone' and 'delete'.
Questions:
- I've set the default window size to 800x600. Good idea or not?
Which TechLevel setting you like better? Scroller(main scr) or dropdown list (teamtype scr)?
- The interface, is the way to edit stuff ok or you want it done differently?
Should the teamtype dropdown in the main screen have team names next to the IDs? So you don't have to click [...] to look at each teamtype's name.
- I remember Cannis sometime ago saying that FA2 writes teamtype properties in an odd way, and includes a couple of obsolete ones. Which might those be, so I
can remove them right now?
Here's a problematic situation:
The trigger uses teamtype A. You click [...] next to A and in that screen modify some of it's properties, without closing, decide to fix another, possibly unrelated, teamtype, say teamtype B, select it in teamtype dropdown, and modify it a bit. When you save and close the secondary screen, should the original trigger be updated to use B instead of A? If so, modifying teamtype B would require you to locate a trigger which uses teamtype B, instead of simply changing to X in the trigger screen. If not, actually wanting to change the teamtype B to A would require you to remember A's ID. I can't figure out the best way to solve this.
The same problem goes for script types and task forces - bind them to teamtypes or not?
I'm thinking of making it like this:
Clicking [...] to open the teamtype screen keeps the teamtype bound.
Using menu to open the teamtype screen does not bind any teamtypes to any triggers.
P.S. Are you guys the only ones interested? When I showed AI Editor 1 and Ini checker, lots of people were interested... Say, where's Renegade? His AI coder complained about the AI editor 1, so let's hear suggestions from him