We have updated the test version of the modeling tool to version 0.96 revision 407:
https://www.anchormodeling.com/modeler/test
Updates in revision 407 (and earlier):
- Fixed bug with restatement control rendered useless in bitemporal models.
- Added restatement control for ties.
- Fixed bug where setInterval was being called too many times in older browsers.
- Replaced setInterval code with setTimeout in older browsers.
- Sped up rendering even further by pushing run once-if-statements to init-functions.
- Added insert triggers on the latest views for ties, with idempotency control.
- Fixed all insert triggers such that when knots are involved, either the ID or the value column from the knot can be used, whereas previously the value column had to be specified.
- Added delete keyboard shortcut ‘d’.
- Added a (long overdue) consistency check for ties, such that roles cannot become “deep-equal”, according to the XML Schema for anchor models.
- Roles in a tie can now have the same name, as long as they do not refer to the same anchor.
- Removed triggers from anchors that have no attributes (to fix broken code generation).
- Temporalization metadata is now recognized when models are loaded.
- Fixed bug that made input fields repeat more than once when selecting bitemporal output.
- Improvements of how knots are handled in the triggers.
- The naming convention now allows upper and lower case Latin-1 characters.
- The naming convention is changed in order to support multiple attributes on the same anchor referencing the same knot. In order to be consistent, the name of the identity in the attribute was changed accordingly.
This change is NOT backwards compatible! - Edit (revision 409 released on Oct 30):
Added an option in the “Defaults” menu to change back to the “Original” naming convention. This quickly became a public request!
Use this with some caution as some changes are not backwards compatible. Should you decide to use this version you cannot go back to a previous version. You cannot mix the output from this version with an existing implementation either, since the naming convention will differ. However, it should be quite easy to migrate to a new version if you have a new and an old implementation side by side.
