Skip to content

Commit 7393778

Browse files
committed
pass 4
1 parent 8466d75 commit 7393778

7 files changed

+26
-22
lines changed

specs/AnimatedVisualPlayer Spec.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -53,8 +53,9 @@ when the player is idle (when `PlayAsync` is not active).
5353
|Resources | AnimatedVisualPlayer will not create animations until `PlayAsync()` is called, and will destroy them when it completes.
5454
If you call pause, this does not free up all resources of the player. To truly stop the animation, call Stop. |
5555

56-
Note: If you set the `Source` or `AnimationOptimization` of your player, the player will defer
57-
processing of the source file until the layout is being formed.
56+
> [!NOTE]
57+
> If you set the `Source` or `AnimationOptimization` of your player,
58+
> the player will defer processing of the source file until the layout is being formed.
5859
5960
If you have an animation that will start on click, you may want to initialize
6061
the property to `None` and set `AnimationOptimization` to 'Always'

specs/DateTimePicker-Visual-Updates-Spec.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -54,9 +54,9 @@ To allow pointer events to get to the source element, set the overlay's
5454
[UIElement.IsHitTestVisible](https://learn.microsoft.com/uwp/api/Windows.UI.Xaml.UIElement.IsHitTestVisible)
5555
property to false.
5656

57-
> Note: the element set as the `SourceElement` cannot be an ancestor or in the descendancy of
58-
the `MonochromaticOverlayPresenter`. However the `SourceElement` must be in the same XAML tree as
59-
the `MonochromaticOverlayPresenter`.
57+
> [!NOTE]
58+
> The element set as the `SourceElement` cannot be an ancestor or in the descendancy of the `MonochromaticOverlayPresenter`.
59+
> However the `SourceElement` must be in the same XAML tree as the `MonochromaticOverlayPresenter`.
6060
6161
If the `ReplacementColor` property is set and has a nonzero Alpha value, then the `SourceElement`
6262
is treated as a mask: every non-transparent pixel will be replaced by this color. The RGB value
@@ -140,7 +140,7 @@ article.
140140
## Other MonochromaticOverlayPresenter members
141141

142142
| Name | Description |
143-
| - | - |
143+
| --- | --- |
144144
| SourceElement | Gets or sets the UIElement to render inside the `MonochromaticOverlayPresenter`. |
145145
| ReplacementColor | Gets or sets the Color to use instead of the non-transparent pixels of the SourceElement.
146146

specs/FooterMenuItemTemplate-spec.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ Example showing how a NavigationView can have different object types for main an
4848
The following APIs are members of `NavigationView`.
4949

5050
| Name | Description |
51-
| - | - |
51+
| --- | --- |
5252
| FooterMenuItemTemplate | Gets or sets the [DataTemplate](https://learn.microsoft.com/uwp/api/windows.ui.xaml.datatemplate) used to display each footer menu item. |
5353
| FooterMenuItemTemplateSelector | Gets or sets a reference to a custom [DataTemplateSelector](https://learn.microsoft.com/uwp/api/windows.ui.xaml.controls.datatemplateselector) logic class. The DataTemplateSelector referenced by this property returns a template to apply to Navigation items placed in the footer menu. |
5454

specs/appwindow-spec.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,20 @@
11
Window.AppWindow API
22
===
33

4-
New API to simplify accessing [AppWindow](https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/windowing/windowing-overview)
4+
New API to simplify accessing [AppWindow](https://learn.microsoft.com/windows/apps/windows-app-sdk/windowing/windowing-overview)
55
functionality through WinUI 3 code.
66

77
# Background
88

99
XAML has a [Window](https://learn.microsoft.com/uwp/api/Windows.UI.Xaml.Window) API that
10-
internally wraps an hwnd. Windows has an [AppWindow](https://learn.microsoft.com/uwp/api/Windows.UI.WindowManagement.AppWindow) class
11-
that similarly wraps an hwnd in UWP. WinAppSDK has a new [AppWindow](https://learn.microsoft.com/windows/windows-app-sdk/api/winrt/Microsoft.UI.Windowing.AppWindow) which wraps an hwnd and works on Desktop.
10+
internally wraps an HWND. Windows has an [AppWindow](https://learn.microsoft.com/uwp/api/Windows.UI.WindowManagement.AppWindow) class
11+
that similarly wraps an HWND in UWP. WinAppSDK has a new [AppWindow](https://learn.microsoft.com/windows/windows-app-sdk/api/winrt/Microsoft.UI.Windowing.AppWindow) which wraps an HWND and works on Desktop.
1212

1313
You can get an AppWindow from a XAML Window by calling a COM API to get XAML and then
14-
a DLL export API to convert the hwnd to an AppWindow. This spec adds a simple `Window.AppWindow`
14+
a DLL export API to convert the HWND to an AppWindow. This spec adds a simple `Window.AppWindow`
1515
property to make this much easier and more discoverable.
1616

17-
[XAML Window](https://learn.microsoft.com/en-us/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.window) will
17+
[XAML Window](https://learn.microsoft.com/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.window) will
1818
expose AppWindow object directly to app developer through an API. Instead of writing a lot of boilerplate
1919
code everywhere, app developer can use this API, reducing code bloat, and making AppWindow APIs easily
2020
accessible from WinUI 3 code.
@@ -73,13 +73,13 @@ an observable behavior change from the behavior before the introduction of this
7373

7474
New subclassing order with this new feature change:
7575

76-
* ContentAppWindowBridge
77-
↓
78-
* AppWindow
79-
↓
80-
* XAML Window
76+
- ContentAppWindowBridge<br/>
8177
&darr;
82-
* DefaultWndProc
78+
- AppWindow
79+
&darr;
80+
- XAML Window
81+
&darr;
82+
- DefaultWndProc
8383

8484
# API Details
8585

specs/public-api-review-process.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ We are committed to respond to all feedback in different manners depending on th
9393

9494
- **Discussion:**
9595

96-
- A “eye” emoji by the author / poster to signify that it is read.
96+
- An “eye” emoji by the author / poster to signify that it is read.
9797

9898
## Consolidate Feedback
9999

specs/xaml-backdrop-api.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -94,7 +94,8 @@ For example:
9494
</Window>
9595
```
9696

97-
Note that `MicaBackdrop` isn't supported on all systems. In such cases a solid color will be used instead of the Mica effect.
97+
> [!NOTE]
98+
> Note that `MicaBackdrop` isn't supported on all systems. In such cases a solid color will be used instead of the Mica effect.
9899
99100
## SystemBackdrop class
100101

specs/xaml-resource-references-tracing-spec.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -119,8 +119,10 @@ Below is an example message from the WinUI Gallery sample app after an incorrect
119119
that the desired resource is defined in `App.xaml`, then the failure to locate it in there is a
120120
strong indicator of an erroneous reference.
121121

122-
Note: The below example output is for illustrative purposes only. The precise format of the message is
123-
implementation-defined and may change in the future. Applications should not attempt to parse the message.
122+
> [!NOTE]
123+
> The below example output is for illustrative purposes only.
124+
> The precise format of the message is implementation-defined and may change in the future.
125+
> Applications should not attempt to parse the message.
124126

125127
```text
126128
Beginning search for resource with key 'OutputTextBlockStyl'.

0 commit comments

Comments
 (0)