Difference between revisions of "CARenderingStyle::NumberAsText"
(Created page with "<< Back to CARenderingStyle = property bool NumberAsText = == Data type == Boolean == Access == read/write = Usage = deftab.CATable::RenderingSt...") |
(Full precision) |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | [[CARenderingStyle | + | [[Category:ADE User Guide]] |
| + | [[ADE User Guide]] > [[ADE Server Class Reference]] > [[CARenderingStyle]] | ||
| + | <languages /> | ||
| + | <translate> | ||
| + | = property bool NumberAsText = <!--T:1--> | ||
| − | + | <!--T:2--> | |
| + | Controls whether numeric results or numeric table cell definitions are returned as floating point | ||
| + | numbers or as formatted strings. When true, the number format for the current object controls | ||
| + | how the number is formatted as a string (except that the [[CARenderingStyle::FullPrecision|FullPrecision]] property can override the | ||
| + | number of digits in the number format). | ||
| − | + | When [[CARenderingStyle::FullPrecision]] is true, all date-time numbers are rendered in a canonical format, effectively ignoring any custom date or time format, so as to ensure that the date and time can be re-parsed correctly. Since dates and times can appear in many different customizations, it isn't just a simple matter of increasing the number of digits to obtain full precision, and hence, it reverts to a canonical form. | |
| + | == Data type == <!--T:3--> | ||
| + | |||
| + | <!--T:4--> | ||
Boolean | Boolean | ||
| − | == Access == | + | == Access == <!--T:5--> |
| + | <!--T:6--> | ||
read/write | read/write | ||
| − | = Usage = | + | = Usage = <!--T:7--> |
| + | |||
| + | <!--T:8--> | ||
| + | deftab.[[CATable::RenderingStyle|RenderingStyle]].[[CARenderingStyle::NumberAsText|NumberAsText]] = true; | ||
| + | deftab.[[CATable::RenderingStyle|RenderingStyle]].[[CARenderingStyle::FullPrecision|FullPrecision]] = false; | ||
| − | + | In general, if you are showing this text to an end-user, you probably want to turn off [[CARenderingStyle::FullPrecision|FullPrecision]], and when writing the values to a data file, you want to turn [[CARenderingStyle::FullPrecision|FullPrecision]] on. | |
| − | = See Also = | + | = See Also = <!--T:9--> |
| + | </translate> | ||
Latest revision as of 21:17, 14 September 2017
ADE User Guide > ADE Server Class Reference > CARenderingStyle
property bool NumberAsText
Controls whether numeric results or numeric table cell definitions are returned as floating point numbers or as formatted strings. When true, the number format for the current object controls how the number is formatted as a string (except that the FullPrecision property can override the number of digits in the number format).
When CARenderingStyle::FullPrecision is true, all date-time numbers are rendered in a canonical format, effectively ignoring any custom date or time format, so as to ensure that the date and time can be re-parsed correctly. Since dates and times can appear in many different customizations, it isn't just a simple matter of increasing the number of digits to obtain full precision, and hence, it reverts to a canonical form.
Data type
Boolean
Access
read/write
Usage
deftab.RenderingStyle.NumberAsText = true; deftab.RenderingStyle.FullPrecision = false;
In general, if you are showing this text to an end-user, you probably want to turn off FullPrecision, and when writing the values to a data file, you want to turn FullPrecision on.
Enable comment auto-refresher