Version 3.0.0 nearly complete
- when using the "Reset to here" function, nodes/edges properties are
correctly saved and restored (note that it was enough to actually get
the property from the hash table doing savedAttrs.get(node).get(attr)
instead of savedAttrs.get(attr), which of course returned null...).
Also network properties are saved (using local tables), so things like
seconds per point and time scale factor are properly recovered
- Some minor syntactic changes were needed to adapt the code to Java 6:
until Cytoscape 3.2 comes out, that is the safest version, because it is
the one used in MacOS when starting Cytoscape with the application icon
(if the variables are properly set, you can start it from the console
using the JVM of choice, but that is currently the only method).
Version 3.0.0 nearly complete
- when using the "Reset to here" function, nodes/edges properties are
correctly saved and restored (note that it was enough to actually get
the property from the hash table doing savedAttrs.get(node).get(attr)
instead of savedAttrs.get(attr), which of course returned null...). Also
network properties are saved (using local tables), so things like
seconds per point and time scale factor are properly recovered
- Some minor syntactic changes (mainly, catches with |) were needed to
adapt the code to Java 6: until Cytoscape 3.2 comes out, that is the
safest version, because it is the one used in MacOS when starting
Cytoscape with the application icon (if the variables are properly set,
you can start it from the console using the JVM of choice, but that is
currently the only method).
- A message has been added in the monitor for ANIMO analysis: now we
also show where exactly the UPPAAL model has been saved, so we can deal
with the strange temporary directory used in Cytoscape 3, which is very
far from any default tmp directory. Also on the same task: now we
explicitly wait for the task, checking every 50 ms (RunAction.java,
lines 403-413) if it has finished. If we don't do this, we consider the
task finished when it is not (apart from other things, we also reset the
error stream to System.err instead of the log file, writing there only
"we took 0 seconds and it's done"), and indeed it starts running after
we finish those things. Currently, there is no better way to have both a
Task Monitor (to show all the nice messages, including the location
where the UPPAAL model was saved) and a synchronously executed task.
- Default value for uncertainty has been set to 0, as we normally
present our models as deterministic, so it would be strange not to be..