From 1749f26437b0c4bf657c6f2f92f9938d2d7d84da Mon Sep 17 00:00:00 2001 From: Dave Parker Date: Tue, 4 Feb 2020 10:25:35 +0000 Subject: [PATCH] Bugfix: Broken GUI path generation when there are undefined constants. Calling code should be calling Prism.setPRISMModelConstants now, after recent changes to the usage of Prism. But the methods in GUISimulator got missed when this was updated elsewhere. --- prism/src/userinterface/simulator/GUISimulator.java | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/prism/src/userinterface/simulator/GUISimulator.java b/prism/src/userinterface/simulator/GUISimulator.java index 5869c993..d9bcab1e 100644 --- a/prism/src/userinterface/simulator/GUISimulator.java +++ b/prism/src/userinterface/simulator/GUISimulator.java @@ -407,7 +407,7 @@ public class GUISimulator extends GUIPlugin implements MouseListener, ListSelect lastConstants = uCon.getMFConstantValues(); lastPropertyConstants = uCon.getPFConstantValues(); // store constants (currently, compute non-exact for simulation) - parsedModel.setUndefinedConstants(lastConstants, false); + getPrism().setPRISMModelConstants(lastConstants, false); pf.setSomeUndefinedConstants(lastPropertyConstants, false); // check here for possibility of multiple initial states @@ -822,7 +822,7 @@ public class GUISimulator extends GUIPlugin implements MouseListener, ListSelect // remember constant values for next time lastConstants = uCon.getMFConstantValues(); // store constants (currently, compute non-exact for simulation) - parsedModel.setUndefinedConstants(lastConstants, false); + getPrism().setPRISMModelConstants(lastConstants, false); // do we need to ask for an initial state for simulation? // no: just use default/random