I was playing with Uppaal 3.6 beta1 pre1 rev. 1625 to reproduce it try: 1) open testsuite.xml (attached) 2) go to simulator 3) pick and fire transition (e.g. one2many: ...) 4) go back to editor, system declarations 5) add env2 process 6) switch to simulator, say yes to update it 7) Caught unexpected ... message box appears. and the terminal is full of traces of course...
Created attachment 93 [details] model to reproduce an exception
Alpha 5 has the same problem. May be caused by the fix for bug 96.
This was introduced in rev. 1569. Robert, that is you change. Can you please take a look at this asap. Thanks.
(In reply to comment #3) > This was introduced in rev. 1569. Robert, that is you change. Can you please > take a look at this asap. Thanks. > I have found the errors. I'll read the code through an extra time and then commit as soon as I get home today.
(In reply to comment #4) > I have found the errors. I'll read the code through an extra time and then > commit as soon as I get home today. That was fast, thanks! How severe is it? That is, how likely is it that our users will run into this problem?
The zoom level of processes and their visibility is remembered in some arrays in the simulator each time the system is reuploaded. I forgot to pay attention to theese arrays changing their size when the system definition is expanded (or reduced for that matter) with additional processes. I have fixed the bug and checked it into SVN as revision 1633.