23.11.2012 Views

2 Visual Components Manuals

2 Visual Components Manuals

2 Visual Components Manuals

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

The following describes how VC 2.2 Runtime performs with scaling and the possibilities available to the user. In<br />

addition, how user settings are processed internally is shown to give the user and developer a better idea of this.<br />

4.13.2.4 Internal Performance<br />

Without having to go too much into detail, two principle VC 2.2 Runtime procedures are described:<br />

− Scaling Output<br />

− Scaling Input<br />

For the most part, code excerpts have been avoided when describing internal processes. Instead, we will try to<br />

explain things using graphics and text alone.<br />

4.13.2.5 Decimal Places<br />

A potentially configured decimal place exerts an exceptional influence on the display value range limits. There is<br />

basically one rule to keep in mind:<br />

The decimal place does not have any effect on the actual calculation. It only has an effect on the format<br />

of the output string which is formed as display output after the values are calculated.<br />

When decimal positions are referred to in the following, it always means the sum from fixed and dynamic<br />

decimal places using PVs.<br />

The decimal place only exerts this aforementioned influence when fixed limit values are scaled. This influence<br />

works in such a way that the maximum display value is greater internally by the number of "zeroes", as decimal<br />

places are present. An example shows this more clearly:<br />

Ex. a)<br />

Field length: 5 Decimal places: 2 Configured maximum display value: 100.33<br />

Internal maximum display value: 10033<br />

Ex. b)<br />

Field length: 5 Decimal places: 2 Configured maximum display value: 100<br />

Internal maximum display value: 10000<br />

Ex. c)<br />

Field length: 5 Decimal places: 2 Configured maximum display value: 1000<br />

When this configuration is attempted, the editor changes this value to 999.99.<br />

This is because it is necessary that the entire maximum value plus the decimal places may not exceed the<br />

maximum field length. From 1000 comes 1000.00 which corresponds to a field length of 6 places à can't be<br />

displayed.<br />

This problem should be taken into account when using dynamic decimal point shifts. Each increase in the<br />

decimal position increases the maximum display value limit by a factor of 10. In turn, this leads to an increase of<br />

places in the display string when entering the configured maximum value.<br />

Ex. a)<br />

Field length: 5 Decimal places: 1 Configured maximum display value: 100<br />

Dynamic decimal point shift: 0<br />

Internal maximum display value: 1000<br />

Input: 100 à 100.0 (4 numeric places) à OK<br />

Introduction to <strong>Visual</strong> <strong>Components</strong> 2.3<br />

440 4.13.2.4 Internal Performance

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!