This issue tracker is closed. Please visit UPPAAL issue tracker at Github instead.

Bug 669

Summary: Variables not sent to simulator
Product: UPPAAL Stratego Reporter: Frederik Baymler Mathiesen <fmathi16>
Component: EngineAssignee: Marius Mikučionis <marius>
Status: ASSIGNED ---    
Severity: major    
Priority: P5    
Version: 4.1.20-6   
Hardware: PC   
OS: Linux   
Architecture:

Description Frederik Baymler Mathiesen 2019-10-15 10:45:06 CEST
In version 4.1.20-6, newly added variables on templates are not sent to the simulator.

To reproduce (MWE):

1. Start new project.
2. Add new state to Template.
3. Add transition from start to the new state.
4. Add `int x = 0;` in Template/declarations.
5. Open simulator.

Now, the variable is not present in variable list. If you save and reopen the project, the variable becomes present in the variable list.

Removing a variable from a declaration does not prompt for uploading the new model to the simulator (and thus it does not remove the variable from the simulator again).
Comment 1 Marius Mikučionis 2019-10-28 15:59:12 CET
I cannot reproduce it with Stratego-6 on Linux, I can see the variable x=0 under Process (it is a local declaration afterall).

Need more details, e.g. is it specific to Windows?
Comment 2 Frederik Baymler Mathiesen 2019-10-28 17:38:32 CET
First of all, it is not Windows specific, as I'm running Ubuntu 18.04.
Second, it is rather peculiar, as the issue is only with my laptop, but not my desktop despite both running Ubuntu 18.04. Any suggestions to what I can test?
Comment 3 Marius Mikučionis 2019-11-05 11:16:42 CET
OK, one step is missing:
one must open the simulator in between step 3 and step 4.

Updated MWE:

1. Start new project.
2. Add new state to Template.
3. Add transition from start to the new state.
4. Open simulator, observe the initial state.
5. Go back to the editor Add `int x = 0;` in Template/declarations.
6. Go to simulator, click "yes" to uopload the new model
7. Observe that the new variable is missing as if it is using the old model.

A workaround is to press F5 to reload the simulator, but it should not be neccessary.