Revision as of 11:09, 10 August 2011 view source Bill Syme (talk \| contribs) Bureaucrats, Administrators 461 edits No edit summary ← Older edit		Revision as of 15:20, 20 June 2022 view source Melissa.Moghanloo (talk \| contribs) Bureaucrats, Administrators 2,918 edits No edit summary Newer edit →
Line 3: \|alt_msg=NA \|type=[[ERROR]] \|message_desc=No <font color="green"><tt>End Define</tt></font> command was found to close of the <font color="~~green~~blue"><tt>Define Event </tt></font><font color="red"><tt>== </tt></font> block for the event. \|suggestions=Check the event file. Add the <font color="green"><tt>End Define</tt></font> command where it is missing. '''Tip:''' When using commands such as <font color="~~green~~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> Line 20: Other examples of commands that benefit from indenting are: * <font color="~~green~~blue"><tt>Start 2D Domain </tt></font><font color="red"><tt>== </tt></font> * <font color="~~green~~blue"><tt>If Scenario </tt></font><font color="red"><tt>== </tt></font> \|discussion_page=* [[Talk:TUFLOW Message 0028\|Discuss Message 0028]]

TUFLOW Message 0028: Difference between revisions