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: components/Adorners/samples/Adorners.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,11 +52,13 @@ The above examples highlights how adorners are sized and positioned directly ato
52
52
53
53
## Custom Adorner Example
54
54
55
-
Adorners can be subclassed in order to encapsulate specific logic and/or styling for your scenario. For instance, you may want to create a custom Adorner that allows a user to edit a piece of text in place:
55
+
Adorners can be subclassed in order to encapsulate specific logic and/or styling for your scenario.
56
+
For instance, you may want to create a custom Adorner that allows a user to click and edit a piece of text in place.
57
+
The following example uses `IEditableObject` to control the editing lifecycle coordinated with a typical MVVM pattern binding:
56
58
57
59
> [!SAMPLE InPlaceTextEditorAdornerSample]
58
60
59
-
Adorners are templated controls, but you can use a class-backed resource dictionary to better enable usage of x:Bind for easier creation.
61
+
Adorners are template-based controls, but you can use a class-backed resource dictionary to better enable usage of x:Bind for easier creation and binding to the `AdornedElement`, as seen here.
[ToolkitSample(id:nameof(InPlaceTextEditorAdornerSample),"In place text editor Adorner",description:"A sample for showing how add a popup TextBox component via an Adorner of a TextBlock.")]
0 commit comments