Appendix C. Common Errors
Symptom - cause - what to do. Collected according to what is most often talked about
they stumble.
The field that was there has disappeared
Reason: visibility condition. The field is shown only when it contains meaning, and includes it in some field higher in the list - usually Mode
or Type.
- What to do
-
Place this field in the desired position. The meaning of the disappeared
the field is not lost: it will return along with the field.
Details: Chapter 11.
The connection disappeared on its own
- Reason
-
the component it pointed to was deleted. Link to non-existent
the editor does not leave the component - the transition property is cleared.
- What to do
-
Ctrl+Z will return both the component and the links. If the deletion was
necessary - set the transition again. Details: Chapter 6.
File "lost" after reboot
- Reason
-
The attachment lives in temporary storage until the end of the connection.
Only saving the script secures it to the server.
- What to do
-
Re-download and save the script. Rule: loaded files are preserved.
Details: Chapter 18.
Variable was not substituted
- Reason
-
most often the name in the expression does not match the name of the variable -
case or typo. Names are case sensitive. What to do:: open the Variables window and look at the counter
mentions. The zero for the variable you think is being used is
and there is an answer. It is better to insert names into expressions from wood rather than print them.
Details: chapters 13 and 15.
The expression falls on a variable
- Reason
-
the variable has no value, and [name] in the expression is a reference
to it: the server throws an exception instead of returning void.
A comparison like [x] == null does not help from this - [x] is already falling.
- What to do
-
check for the presence of a value using the
check_variable("x")function
or take the default value - get_variable_value("x", "").
Usually it doesn’t come to this: Start sets up variables by default
with empty values of their types - but if this behavior is changed
setup, checking is needed.
Details: Chapter 15.
Call ends after transfer
- Reason
-
the translation does not have spare branches filled in. The operator did not answer
and there is nowhere to go.
- What to do
-
fill in at least Transition, time and Transition, refusal.
Details: Chapter 16.
Trace breaks at transition
- Reason
-
this is not a break. Going by a label is not a connection: it is looking for a label
by name, and not by the drawn arrow, and the trace does not follow it.
What to do: check such transitions by searching by tag name. Found
only a link and not a single label - that’s when it really breaks down.
Details: chapters 9 and 20.
Arrows move the map, not the components
Reason: arrows without a modifier are scrolling the field. Components
moves Alt with arrow.
- What to do
-
hold kbd: [Alt]. And check that the focus is on the card field,
and not in the input field of the panel. Details: Chapter 5.
Extended connection from “Menu” - “Other” was filled in
Reason: Ctrl pulls the main branch of the type, and the main branch of the menu is
this is “where to go if no value matches.”
- What to do
-
value branches are specified by the Values table, and not by the mouse. Details: Chapter 16.
==Can’t save
- Reason
-
one of three - no connection, the version on the server is newer, not fixed
attachments. The editor will tell you which one it is.
- What to do
-
if there is a break, wait for recovery; in case of conflict, look history and decide whose edits to apply; save for unattached files
one more time.
Details: chapters 22 and 23.
Half of the card went dark
- Reason
-
branch tracing (T) or change highlighting is enabled from version history.
- What to do
-
Esc.
Details: chapters 20 and 24.