Closed rensink closed 2 weeks ago
The simplicity property message is not the root of the problem - something happened in the SimulatorModel, a transaction was started that was not finished. Added try - finally to all start/finish pairs in the SimulatorModel in an attempt to avoid this in the future; without further information, it's the best I can do
This can be reproduced in the enclosed rule system by editing and then saving one of the enabled start graphs. The graph is actually saved (as can be discovered by restarting GROOVE) but the reported crash happens.
Apparently, a just-edited host graph (more precisely, its AspectGraph) was marked as "simple" whereas they are not "simple" when loaded. This discrepancy emerges only when merging multiple start graphs into one, specifically after editing one of them. Rather than marking this as a conflict, the solution is now to make the merged graph non-simple as soon as one of the operands is non-simple.
The precise circumstances are not clear. Here's a stack trace: