So here's version 0.4 of my little FPI script editor. Screenshot here (shows the variables support):
http://www.xldevelopment.net/ss/fpimaker0.4.png
The highlights of this version are:
-Save is fixed now and will work with all computers
-I have partially implemented my variables idea (view the screenshot)
-Fixed all issues with the settings dialog
-The toolbars and windows now remember their last positions so you can arrange them to your liking
You will need the .NET 1.1 framework which you can get here if you don't already have it:
http://msdn.microsoft.com/netframework/downloads/framework1_1/
Now a short tutorial on using variables.
The idea behind variables is to help you when editing larger scripts that require a lot of state values. The variable simply replaces the number to give it more meaning, making it easier for you to remember what you were doing. They don't only apply to the state command, you can declare a variable for any command that requires a parameter. To use variables you will need to declare them and tell FPI Maker that the script is using variables. You do that buy adding the command:
;Variables=On
(all variable stuff is in comments so it will not interfere with FPS Creator in any way)
You then need to declare a variable. The declaration format is:
;declare (command to associate with variable) #(variable name)=(variable value)
So lets say that we wanted to declare a variable named "stopped" to use for the state command to represent the value of 20, we would type:
;declare state #stopped=20
or if we wanted to declare a sound to use with the 3dsound command we would type:
;declare 3dsound #mysound=audiobanksoundsomesound.wav
After you have declared your variables, you can just use the variable names to represent the values when typing the script. ex:
:state=#stopped:3dsound=#mysound
so the final script might look something like this:
;My FPI Variable Script
;Variables=On
;declare state #stopped=20
;declare 3dsound #mysound=audiobanksoundsomesound.wav
;Header
desc = Variables sample
;Triggers
:state=#stopped:3dsound=#mysound
;End FPI Script
That is basically how you use the FPI Maker variables. They are only partially implemented so you have to manually turn them on and off after loading a script and before saving one. You don't want to save a script with the variables left on because FPS Creator won't understand them. Use the Add Variables/Remove Variables in the Tools Menu to show them and then to convert the values back to be used with FPS Creator. If I did nothing but confuse you with this little tutorial then feel free to email me for a better explanation. Variables is just an enhancement that FPI Maker has, you don't have to use them if you don't want to, you can still use all the other great features of FPI Maker.
Now go download it here:
http://www.xldevelopment.net/download.php?id=FPIMaker0.4.exe
Enjoy.
-Ruben
Download FPI Maker: [href]www.xldevelopment.net/download.php?id=FPIMaker0.4.exe[/href]