-
Git bisect says this was introduced in d531233e70948988b0b117a231500f213bc96f87. Output for `-t json` started failing with that commit like this:
```
$ java -jar org.alloytools.alloy.dist/target/o…
-
The `-t json` option is a great idea! However, it doesn't appear to be outputting instances. I've done this testing off of #249, which appears to be the most functional current branch.
Here is a co…
-
In Alloy 6.1.0, the Execute menu includes a choice to Show Parse Tree, which opens a tree-display widget. This is convenient for clarifying just how some possibly problematic expression has been pars…
-
When considering past operators, the value of expressions may change depending on which loop unrolling it is being evaluated. Instances in the visualizer only have the value of the prefix (and the loo…
-
@pkriens in commit 654e00b, when running command `exec` (without further argument) on the following model, an exception is raised:
```
enum State { Idle, Wait, Crit }
sig Process {
var s…
-
When opening the Visualizer, every sig has the same shape and color by default. It would be more readable if every sig was assigned a distinct color from scratch. Doing this only would make diagrams m…
-
Alloy 6.1.0, Mac OS 13.6.3
In the Evaluator, sometimes the variable name will raise error, The name cannot contain the '$' symbol.
{Node$0} ---> work fine
{Node$1} ---> work fine
{Node$0} + {N…
-
"Export to predicate" (in the Visualizer) issues a wrong predicate. E.g. for the following model, after hitting "fork" then "next state" several times:
```
sig S { var r: S }
run { some disj s1, s2…
-
When selecting text of previous commands in the Evaluator (using double-click), the selection isn't highlighted (but does work as you can, e.g. copy paste the said text with `ctrl+C/ctrl+V`).
-