You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Documentation/topics/editors/editboxes/datetimeeditbox.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -113,6 +113,15 @@ This edit box has multiple parts:
113
113
114
114
When the caret is over a part, the part value may be incremented or decremented. Please see the [Edit Box Basics](parteditboxbase.md) topic for information on how to do this.
115
115
116
+
## Parsing
117
+
118
+
When text is entered directly into the control, the value is initially parsed based on the current [Format](xref:@ActiproUIRoot.Controls.Editors.DateTimeEditBox.Format). If unsuccessful, additional date formats will be attempted.
119
+
120
+
The [ParsingStyles](xref:@ActiproUIRoot.Controls.Editors.DateTimeEditBox.ParsingStyles) property, which defaults to `DateTimeStyles.AllowWhiteSpaces`, can be used to provide additional control over how values are parsed, including options such as which time zone is applied when one is not specified.
121
+
122
+
> [!WARNING]
123
+
> When setting [ParsingStyles](xref:@ActiproUIRoot.Controls.Editors.DateTimeEditBox.ParsingStyles) to a new value, it is recommend to OR the value with `DateTimeStyles.AllowWhiteSpaces` or else white space may not be parsed correctly. For example, to assume UTC when no time zone is specified and keep the default white space handling, set [ParsingStyles](xref:@ActiproUIRoot.Controls.Editors.DateTimeEditBox.ParsingStyles) to `DateTimeStyles.AllowWhiteSpaces | DateTimeStyles.AssumeUniversal`.
124
+
116
125
## Sample XAML
117
126
118
127
This control can be placed within any other XAML container control, such as a `Page` or `Panel` with this sort of XAML:
Copy file name to clipboardExpand all lines: Documentation/topics/licensing.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -170,7 +170,7 @@ The contents of a *licenses.licx* file are pretty simple. It needs a single lin
170
170
This single line (update the version to match the one you use) should be added to the *licenses.licx* file in any project that uses Actipro @@PlatformName control or SyntaxEditor add-on products:
The [Title](xref:@ActiproUIRoot.Controls.Card.Title) and [Description](xref:@ActiproUIRoot.Controls.Card.Description) properties can be used to define a header with a default template where the[Title](xref:@ActiproUIRoot.Controls.Card.Title) is displayed with typography consistent with a heading, and the [Description](xref:@ActiproUIRoot.Controls.Card.Description), if defined, is displayed immediately below it.
97
+
By default, the [Header](xref:@ActiproUIRoot.Controls.Card.Header) property is undefined. Instead, a default [HeaderTemplate](xref:@ActiproUIRoot.Controls.Card.HeaderTemplate) is provided which utilizes `TextBlock` controls to display the [Title](xref:@ActiproUIRoot.Controls.Card.Title) and [Description](xref:@ActiproUIRoot.Controls.Card.Description) properties. The[Title](xref:@ActiproUIRoot.Controls.Card.Title) is displayed with typography consistent with a heading, and the [Description](xref:@ActiproUIRoot.Controls.Card.Description), if defined, is displayed immediately below it.
98
98
99
99
@if (avalonia) {
100
-
Use the [TitleTheme](xref:@ActiproUIRoot.Controls.Card.TitleTheme) and [DescriptionTheme](xref:@ActiproUIRoot.Controls.Card.DescriptionTheme) properties to customize the appearance of each element.
100
+
Use the [TitleTheme](xref:@ActiproUIRoot.Controls.Card.TitleTheme) and [DescriptionTheme](xref:@ActiproUIRoot.Controls.Card.DescriptionTheme) properties to customize the appearance of each `TextBlock`element in the default [HeaderTemplate](xref:@ActiproUIRoot.Controls.Card.HeaderTemplate).
101
101
}
102
102
@if (wpf) {
103
-
Use the [TitleStyle](xref:@ActiproUIRoot.Controls.Card.TitleStyle) and [DescriptionStyle](xref:@ActiproUIRoot.Controls.Card.DescriptionStyle) properties to customize the appearance of each element.
103
+
Use the [TitleStyle](xref:@ActiproUIRoot.Controls.Card.TitleStyle) and [DescriptionStyle](xref:@ActiproUIRoot.Controls.Card.DescriptionStyle) properties to customize the appearance of each `TextBlock`element in the default [HeaderTemplate](xref:@ActiproUIRoot.Controls.Card.HeaderTemplate).
104
104
}
105
105
106
106
The following example demonstrates creating a [Card](xref:@ActiproUIRoot.Controls.Card) with both [Title](xref:@ActiproUIRoot.Controls.Card.Title) and [Description](xref:@ActiproUIRoot.Controls.Card.Description) defined:
Alternatively, the [Header](xref:@ActiproUIRoot.Controls.Card.Header) can be set to any value supported by `ContentPresenter`. In this case, the explicit content will be used instead of the default template based on the [Title](xref:@ActiproUIRoot.Controls.Card.Title) and [Description](xref:@ActiproUIRoot.Controls.Card.Description) properties.
128
128
129
-
The following example demonstrates creating a [Card](xref:@ActiproUIRoot.Controls.Card) with an explicit [Header](xref:@ActiproUIRoot.Controls.Card.Header) defined:
129
+
> [!IMPORTANT]
130
+
> The [Title](xref:@ActiproUIRoot.Controls.Card.Title) property is not the same as the [Header](xref:@ActiproUIRoot.Controls.Card.Header) property. It is only a `string` property that, along with the [Description](xref:@ActiproUIRoot.Controls.Card.Description) property, can be used by elements in a [Header](xref:@ActiproUIRoot.Controls.Card.Header) or [HeaderTemplate](xref:@ActiproUIRoot.Controls.Card.HeaderTemplate).
130
131
131
132
@if (avalonia) {
133
+
The following example demonstrates creating a [Card](xref:@ActiproUIRoot.Controls.Card) with an explicit [Header](xref:@ActiproUIRoot.Controls.Card.Header) defined and whose `TextBlock` applies the [TitleTheme](xref:@ActiproUIRoot.Controls.Card.TitleTheme):
The following example demonstrates creating a [Card](xref:@ActiproUIRoot.Controls.Card) with an explicit [Header](xref:@ActiproUIRoot.Controls.Card.Header) defined and whose `TextBlock` applies the [TitleStyle](xref:@ActiproUIRoot.Controls.Card.TitleStyle):
> The default [HeaderTemplate](xref:@ActiproUIRoot.Controls.Card.HeaderTemplate) (that uses the [Title](xref:@ActiproUIRoot.Controls.Card.Title) and [Description](xref:@ActiproUIRoot.Controls.Card.Description) properties) is only applied when the [Header](xref:@ActiproUIRoot.Controls.Card.Header) has not been explicitly defined, so there is no need to clear the default [HeaderTemplate](xref:@ActiproUIRoot.Controls.Card.HeaderTemplate) when defining a custom [Header](xref:@ActiproUIRoot.Controls.Card.Header).
171
+
162
172
### Thumbnail
163
173
164
174
The [Thumbnail](xref:@ActiproUIRoot.Controls.Card.Thumbnail) is displayed in the header area, but is separate from the [Header](xref:@ActiproUIRoot.Controls.Card.Header) content. [Thumbnail](xref:@ActiproUIRoot.Controls.Card.Thumbnail) can be set to any value supported by `ContentPresenter` but is typically used to display a small image.
0 commit comments