|
skorpion59
|
|
Tulsa, Oklahoma, USA
May 1999 time: 23:13
|
|
Gemini,
It is best to put your code in your own files. For the SLIC code, use gemini.slc and put in (CTP)\ctp_data\default\gamedata. Then edit script.slc (in same directory) and put #include "gemini.slc" at the bottom of the file.
For your strings, make gemini_str.txt and put in (CTP)\ctp_data\english\gamedata. Then edit strings.txt (in same directory) and put import "gemini_str.txt" at the top of the file.
You are correct. Text(ID_This_Is_Text_A) is the text for the messagebox and Title(ID_This_Is_Text_B) is the title for the messagebox. Both of these display the text pointed to by the string ID, This_Is_Text_A or This_Is_Text_B. String IDs are always preceeded by ID_. All you have to know is to put ID_ before the name of the message you used in your gemini_str.txt file when you make the call. Buttons are string IDs also. For example:
Gemini.slc: code would look like,
Text(ID_This_Is_Text_A);
Title(ID_This_Is_Text_B);
Button(ID_Name_On_Button);
Gemini_str.txt: message would look like,
This_Is_Text_A "This is what displays in the text area."
This_Is_Text_B "This is what displays in the title area."
Name_On_Button "This is what displays on the button."
To show values in a message, use the built-in variable (ie, city.name) or the user defined global variable (ie, gv_population) with .value attached to it. For example:
Shows_Variable_Data "The population of [city.name] is [gv_population.value]."
Hope this helps and you can understand it. If not, let me know.
BTW, the SLIC docs is still being worked on. I ran into some problems which caused me to push back the release. Should be soon though.
------------------
Don, Apolyton Junkie
|