Analytica 5.1 beta Release Notes/Changes in 5.1.4

This page lists changes in the beta 5.1.4 build of Analytica and ADE that have occurred since the 5.1.3 beta build.

Cell formats in tables

When a text-box input control is sized to be tall enough, the text box now allows multiple lines of text (formerly, text box controls on diagrams were limited to a single line of text).
When an output node was showing a scalar value, the field width resizer wasn't allowing you to resize the field width.
When you hold down the Shift key while pressing the hover icon, it jumps to the textual definition instead of the edit table window. This is now consistent with Shift+ on the toolbar.
When you first create a user-input node for a MultiChoice, the control's field width would be too narrow to fully accommodate the "«Multiple»" label.

Bug in Max(x,I,J,K) in which it did not property reduce one of the indexes. The bug appeared in beta build 5.1.3.
Bug in which GetFract(x,[0.05,0.95]) incorrectly changed the implicit index values to [50,950] in the result. Occurred when an explicit list was passed as the «p» parameter.
Added a new built-in function, TableJoin. Currently "experimental" status, not exposed.

The patterns #d, #w, #wd, #wd+, , #wd-, , #h, , #m and #s can now be used in a custom date format. These are the same as in DatePart (see DatePart for more).

Machine-specific crash when viewing a Choice drop-down.
A model file would disappear from the recent file list when you abort the load and the location it had been previously saved to is different from the location where it is being loaded from.
Hanging bug when drawing a text in a result table cell with millions of characters.
When you use the UI to change a list definition into a MultiChoice, it now sets returnList:true automatically and copies the list items to the domain.
The FileInfo attribute on the model's Object window wasn't adjusting its width to the width of the window, and would sometimes truncate the visible file name. Also, the value was a pixel too high in the window.

When DefineOptimization is in a Dynamic loop, the algorithm that infers intrinsic indexes for decision variables when you haven't explicitly specified the intrinsic indexes now infers the Time index to be extrinsic, which better matches the fact that it is in a dynamic loop.
When a decision variable had its number format set with "show separators" on, the values logged to the «traceFile» was including commas in the numbers. Since the array values are separated by commas, you couldn't see where the number boundary was. Numbers are now logged without thousand separators to avoid that confusion.