TUFLOW Message 0028: Difference between revisions
Content deleted Content added
No edit summary |
No edit summary |
||
| (9 intermediate revisions by 2 users not shown) | |||
Line 3:
|alt_msg=NA
|type=[[ERROR]]
|message_desc=No <font color="
|suggestions=Check the event file. Add the <font color="
'''Tip:''' When using commands such as <font color="blue"><tt>Define Event </tt></font><font color="red"><tt>== </tt></font> indent the commands within the block that follows as this makes it much easier to interpret which commands apply to which event definition. For example:
<tt>
<font color="blue">Define Event Name </font><font color="red">== </font>100y
:<font color="blue">BC Event Source </font><font color="red">== </font>_ARI_ <nowiki>|</nowiki> 100y
:<font color="blue">Output Folder </font><font color="red">== </font> ..\results_100y
<font color="blue">End Define</font>
<font color="blue">Define Event Name </font><font color="red">== </font>06h<br>
:<font color="blue">BC Event Source </font><font color="red">== </font> _Durn_ <nowiki>|</nowiki> 06h
:<font color="blue">End Time </font><font color="red">== </font> 9
<font color="blue">End Define</font></tt>
Other examples of commands that benefit from indenting are:
* <font color="blue"><tt>Start 2D Domain </tt></font><font color="red"><tt>== </tt></font>
* <font color="blue"><tt>If Scenario </tt></font><font color="red"><tt>== </tt></font>
|uplink=[[0xxx_TUFLOW_Messages|0xxx Messages]]
}}
| |||