Difference between revisions of "TUFLOW Message 0030"
| (3 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
|alt_msg=NA | |alt_msg=NA | ||
|type=[[ERROR]] | |type=[[ERROR]] | ||
| − | |message_desc=These two commands cannot be used together. Event text definitions can only be defined using one of these commands. <font color="blue"><tt>BC Event Source </tt></font><font color="red"><tt>== </tt></font> became available with the 2010-10 release and allows multiple event texts to be specified for assigning different event names to different boundaries, and is much more powerful than <font color="blue"><tt>BC Event Text </tt></font><font color="red"><tt>== </tt></font> which only allows one event text at any one time within the model. Also see [[TUFLOW Message 0031|Message 0031]]. | + | |message_desc=These two commands cannot be used together. Event text definitions can only be defined using one of these commands. <font color="blue"><tt>BC Event Source </tt></font><font color="red"><tt>== </tt></font> became available with the 2010-10 release and allows multiple event texts to be specified for assigning different event names to different boundaries, and is much more powerful than <font color="blue"><tt>BC Event Text </tt></font><font color="red"><tt>== </tt></font> which only allows one event text at any one time within the model. Also see <u>[[TUFLOW Message 0031|Message 0031]]</u>. |
This message occurs when <font color="blue"><tt>BC Event Source </tt></font> occurs after a <font color="blue"><tt>BC Event Text</tt></font>. [[TUFLOW Message 0034|Message 0034]] occurs when <font color="blue"><tt>BC Event Text </tt></font> occurs after a <font color="blue"><tt>BC Event Source</tt></font>. | This message occurs when <font color="blue"><tt>BC Event Source </tt></font> occurs after a <font color="blue"><tt>BC Event Text</tt></font>. [[TUFLOW Message 0034|Message 0034]] occurs when <font color="blue"><tt>BC Event Text </tt></font> occurs after a <font color="blue"><tt>BC Event Source</tt></font>. | ||
|suggestions=Rework the commands so that only one of the above commands exists. Note, there is no limit to the number of times either of these commands is specified in a model, they just can't both exist in the same model. | |suggestions=Rework the commands so that only one of the above commands exists. Note, there is no limit to the number of times either of these commands is specified in a model, they just can't both exist in the same model. | ||
| − | + | <br> | |
| − | + | ||
| − | |||
| − | |||
|uplink=[[0xxx_TUFLOW_Messages|0xxx Messages]] | |uplink=[[0xxx_TUFLOW_Messages|0xxx Messages]] | ||
| − | |||
}} | }} | ||
Latest revision as of 10:00, 22 December 2022
TUFLOW Message
ERROR 0030 - Cannot use "BC Event Source" and "BC Event Text" together.
Alternate Message
NA
Message Type
ERROR
Description
These two commands cannot be used together. Event text definitions can only be defined using one of these commands. BC Event Source == became available with the 2010-10 release and allows multiple event texts to be specified for assigning different event names to different boundaries, and is much more powerful than BC Event Text == which only allows one event text at any one time within the model. Also see Message 0031.
This message occurs when BC Event Source occurs after a BC Event Text. Message 0034 occurs when BC Event Text occurs after a BC Event Source.
Suggestions
Rework the commands so that only one of the above commands exists. Note, there is no limit to the number of times either of these commands is specified in a model, they just can't both exist in the same model.
| Up |
|---|
 0xxx Messages
|