Scripts (in prims) containing syntax errors cannot be saved. This is a change in behaviour from 1.23.4.93100
Case 1 - closing script editor after using "Save":
- Add a default script to a prim
- Modify the script so that it contains a syntax error
For Example:
default
{
state_entry()
{
llSay(0, "Hello, Avatar!"); xxxxxxxxxxxxxxxxxxxxxxxxx
}
touch_start(integer total_number)
{
llSay(0, "Touched.");
}
}
- Observe: "ERROR: Syntax error" [as expected]
- Close the script editor window using the top-right X
- Observe: The script is no longer running [as expected]
- Observe: The script no longer contains the syntax error (xxxxxxxxxxxxx if you used the above example)
= Expected: The modified script should have been saved
---------------------------------------------
Case 2 - closing script editor without pressing "Save", then choosing "Save" from pop-up:
- Add a default script to a prim
- Modify the script so that it contains a syntax error
- Attempt to close the script editor using the top-right X
- Observe: "Save Changes?" pop-up, with Save / Don't Save / Cancel options [as expected]
- Observe: The script is no longer running [as expected]
- Observe: The script no longer contains the syntax error (xxxxxxxxxxxxx if you used the above example)
= Expected: The modified script should have been saved
------------------
NOTE: Scripts in inventory (not in a prim) appear to save correctly even if they contain a syntax errors.
Bug
Resolved
Major
Mono Beta: Script editor "Save" does not save scripts containing syntax errors
Script containing a syntax error is now saved; the "Running" box is unchecked, but
the "Mono" box is also unchecked.
Is this intentional?