in Lycia Form Designer
century is applied to widgets to which dates can be entered. Specifies how to expand the date if it was abbreviated to one or two digits.
|
in Lycia Form Designer |
|
|
Form XML code:
<Calendar identifier="cvN" century="Current">
By default, century is not specified and, thus, is absent from the form XML code. The property value will appear in the form XML code only once it is specified.
Possible values:
Default value: not specified
Associated containers, widgets and theme elements:
Influence and behavior:
|
Closest |
the year entered is expanded to the nearest date in a past, future, or current century:
Current date: 1/15/2016 User enters: 1/20/16 Current century prefix – 20: 1/20/2016 Nearest past century prefix – 19: 1/20/1916 Nearest future century prefix – 21: 1/20/2116 Logics: Of the three, 1/20/2016 is closest to the current date. Resulting expansion: 1/10/2016
|
|
Past |
the year entered is expanded to the nearest date which is definitely in the past:
Current date: 1/15/2016 User enters: 1/20/16 Current century prefix – 20: 1/20/2016 Nearest past century prefix – 19: 1/20/1916 Logics: Only one variant is definitely in the past, 1/20/1916. Resulting expansion: 1/20/1916
|
|
Future |
the year entered is expanded to the nearest date which is definitely in the future:
Current date: 1/15/2016 User enters: 1/20/16 Current century prefix – 20: 1/20/2016 Nearest future century prefix – 21: 1/20/2116 Logics: Both variants are definitely in the future, but 1/20/2016 is closer to the current date. Resulting expansion: 1/20/2016
|
|
Current |
the year entered is prefixed with the digits of the current century:
Current date: 1/15/2016 User enters: 1/20/16 Current century prefix – 20: 1/20/2016 Resulting expansion: 1/10/2016
|
Related articles:
DBCENTURY