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
description: TODO: Your experiment's description here
4
+
description: An animation helper that morphs between two controls.
5
5
keywords: TransitionHelper, Control, Layout
6
6
dev_langs:
7
7
- csharp
@@ -11,54 +11,11 @@ discussion-id: 0
11
11
issue-id: 0
12
12
---
13
13
14
-
<!-- To know about all the available Markdown syntax, Check out https://docs.microsoft.com/contribute/markdown-reference -->
15
-
<!-- Ensure you remove all comments before submission, to ensure that there are no formatting issues when displaying this page. -->
16
-
<!-- It is recommended to check how the Documentation will look in the sample app, before Merging a PR -->
17
-
<!-- **Note:** All links to other docs.microsoft.com pages should be relative without locale, i.e. for the one above would be /contribute/markdown-reference -->
18
-
<!-- Included images should be optimized for size and not include any Intellectual Property references. -->
19
-
20
-
<!-- Be sure to update the discussion/issue numbers above with your Labs discussion/issue id numbers in order for UI links to them from the sample app to work. -->
21
-
22
14
# TransitionHelper
23
15
24
-
TODO: Fill in information about this experiment and how to get started here...
25
-
26
-
## Custom Control
27
-
28
-
You can inherit from an existing component as well, like `Panel`, this example shows a control without a
29
-
XAML Style that will be more light-weight to consume by an app developer:
30
-
31
-
> [!Sample TransitionHelperCustomSample]
32
-
33
-
## Templated Controls
34
-
35
-
The Toolkit is built with templated controls. This provides developers a flexible way to restyle components
36
-
easily while still inheriting the general functionality a control provides. The examples below show
37
-
how a component can use a default style and then get overridden by the end developer.
38
-
39
-
TODO: Two types of templated control building methods are shown. Delete these if you're building a custom component.
40
-
Otherwise, pick one method for your component and delete the files related to the unchosen `_ClassicBinding` or `_xBind`
41
-
classes (and the custom non-suffixed one as well). Then, rename your component to just be your component name.
42
-
43
-
The `_ClassicBinding` class shows the traditional method used to develop components with best practices.
0 commit comments