If you have a stopping criterion set on a MonitorStat (e.g.,
stopping when MAX activation exceeds some threshold in the output
layer), then this stopping criterion will be lost when you load the
project. If you look in the spew of messages generated during the
load process, you'll see a message like this:
*** Member: mon not found in type: MonitorStat (this is likely just
harmless version skew)
<>{name="max_act_Output": disp_opts=" ": is_string=false:
vec_n=0: val=0: str_val="": stopcrit={flag=true: rel=GREATERTHAN:
val=.5: cnt=1: n_met=0: }: };<<- err_skp>>
Just get the stopcrit value (val=.5 in this example) and
relationship (GREATERTHAN) from this and enter it into the first
element in the mon_vals list in the appropriate MonitorStat in the
opened project to restore function (or replace this stat entirely
with a new ActThreshRTStat).
GraphLog FIXED ranges will be lost upon loading: there is now a
fix_min and fix_max flag inline with the ranges that will need to be
clicked as appropriate (the range values are preserved, just the
flag to fix them is missing). Look for FIXED messages in the spew
as per above.
SelectEdit (.edits) labels will be lost upon loading, and can be
recovered in the same manner as above.
NetView Layer fonts will be smaller than before -- use
View:Actions/Set Layer Font to set a larger font. The new default
for new views is 18 point.
For your additional C++ code: El() function on Lists/Groups/Arrays
renamed to SafeEl() to better reflect its function (index range
checking), and [] operator changed to FastEl() (no index range
checking) instead of SafeEl(), to better reflect typical usage.
Error functions in BP: if you've written your own, see comments in
ChangeLog (search for date 2002-09-13).