Known issues in version 4.4

The following post is obsolete, as the issue was fixed with library version 4.4.1

<OBSOLETE>
A bug has, unfortunately, been introduced in showValues.

The effect is that the supplied field-value associations are managed in a wrong way in the related invocation of the onChangingValues callback,
though the only impact is on the behavior of getServerValue, when invoked on the received VisualUpdateInfo object.

Actually, the value related to the field that precedes (according to the current schema) the one specified is returned.
The bug occurs regardless that the fields (either in showValues or in getServerValue) are specified by name or by number.

Hence, the only temporary workaround feasible is to supply the name of the next field (or the field number increased by 1) in place of the requested one. Using the number also allows for getting the value of the last field.
However, only VisualUpdateInfo objects originated by showValues are affected: objects that carry normal updates from the Server are not affected.
Note that setFormattedValue is also not affected, so the correct field name should be specified there.
</OBSOLETE>

The following issue introduced in version 4.4 affects showValues.

Despite one should be able to call showValues at any time during the lifetime of a table (i.e. after addTable and before removeTable),
the call will be refused in case the Engine is currently disconnected or still connecting and an exception will be thrown to the caller.

Hence, any use of showValues as a means to populate the table at startup will probably fail with an exception.
On the other hand, any use of showValues to modify a table while data is coming will work, but it might throw an exception as well, as soon as a disconnection occurred.