Analytica 5.4 beta Release Notes/Changes in 5.4.3
This page lists all changes in the beta build 5.4.3 that have occurred since the previous beta build 5.4.2.
- First 5.4 beta release to include ADE. Fixed remaining issues with the ADE installer that was preventing release of ADE.
- When copying table cells from a result table in one Analytica instance to an edit table in a different Analytica process, it now copies the actual image (and not just the text «Picture(PNG)»).
- In some cases, when a ProbTable node was copied, the domain index was not also duplicated, causing the new node to use the previous node's index domain.
- There is now a NodeBorderColor attribute, making it possible to alter the border color of nodes. You can set this on class objects to change the default border color for all nodes of that class. There is not GUI for setting this attribute at this time -- you can only change it via the Typescript window. As an example, this typescript command changes module nodes to use a blue border:
NodeBorderColor Module: 0x0000FF
- We foresee this may be incorporated into some new
*.anaStylenode style templates.
Object Window or Attribute Panel
- When you select a node and view its Definition, it has historically selected the entire Definition initially (i.e., causing the entire Definition to start in reverse video). We changed this since we've observed it is rare that you want to replace the entire Definition, so instead it now just puts the caret within the definition.
- Fixed a bug where, when entering a multi-line value into a list cell, the end of the list became invisible (clipped).
File Saving and Loading
- When you use Add Module... to add a Model to your model, it asks whether you want to import the system settings from the incoming model, or just keep your current settings. Previously this did not apply to custom node styles, which were always imported, but now are imported only when you choose to import the system settings from the incoming file.
- Moving a linked module or linked library to a different module shouldn't dirty the linked module or linked library (the only changes are to the parent), so if that is all you did, it shouldn't try to save the linked library when you save your model. Moving the linked module/library no longer dirties the linked module/library.
- A serious (but rare) situation occurred in which it became impossible to save changes. A index evaluation was necessary, but had an error, which caused the save to abort. The fix now successfully saves.
- A change to (only) the button style (in Diagram Style...) previously did not dirty the model (so the Save option didn't enable).
The new feature that underlines syntax errors in a definition occasionally gets it wrong, and underlines some less common but valid expressions. This continues to be worked on. In this build:
Self[Time-1]in a Dynamic was getting underlined.
- Subscript syntax with a «defVal» was being underlined (e.g.,
- Sped up the between-keystrokes coloration processing.
- Handles to class objects (e.g.,
Handle(Module)) previously used the syntax color for a user-defined object. Should have been system object color.
- A local index identifier was given "undefined" syntax coloring.
- The property or method name that comes after the arrow in
comObj->method(...)had been colored as undefined, is now black.
- The Keelin distribution function wasn't working in the previous beta build.
- When the Att_ResultSliceState attribute has an error, the graph accessed via ADE didn't display correctly -- it ignored the graph setup.
- Fixed a situation in which a change to the Common Index role didn't stick. The case occurred when the X-axis variable does not vary with the newly selected Common Index. The "smart pivot" heuristics excluded this as non-sensible and reset the common index.