Skip to content

Commit cb1adbc

Browse files
niels9001Copilot
andcommitted
Fix broken file links in moved pages (batch 2)
Fix relative paths for files moved to develop/ui/ and develop/ui/navigation/: - layouts-with-xaml.md: responsive-design and screen-sizes links - navigate-between-two-pages.md: start-here, page-transitions, navigation-basics - navigation-history-and-backwards-navigation.md: title-bar, navigation-basics - shadows.md: control links (ui/controls/ → controls/) Co-authored-by: Copilot <[email protected]>
1 parent ff6bf10 commit cb1adbc

4 files changed

Lines changed: 20 additions & 20 deletions

File tree

hub/apps/develop/ui/layouts-with-xaml.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ dev_langs:
1111
---
1212
# Responsive layouts
1313

14-
The XAML layout system provides automatic sizing of elements, layout panels, and visual states to help you create a responsive UI. With a responsive layout, you can make your app look great on screens with different app window sizes, resolutions, pixel densities, and orientations. You can also use XAML to reposition, resize, reflow, show/hide, replace, or re-architect your app's UI, as discussed in [Responsive design techniques](responsive-design.md). Here, we discuss how to implement responsive layouts with XAML.
14+
The XAML layout system provides automatic sizing of elements, layout panels, and visual states to help you create a responsive UI. With a responsive layout, you can make your app look great on screens with different app window sizes, resolutions, pixel densities, and orientations. You can also use XAML to reposition, resize, reflow, show/hide, replace, or re-architect your app's UI, as discussed in [Responsive design techniques](../../design/layout/responsive-design.md). Here, we discuss how to implement responsive layouts with XAML.
1515

1616
## Fluid layouts with properties and panels
1717

@@ -135,7 +135,7 @@ To apply a visual state from code, you call the [**VisualStateManager.GoToState*
135135
Here, a [**VisualStateGroup**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.visualstategroup) contains two VisualState definitions. The first, `DefaultState`, is empty. When it's applied, the values defined in the XAML page are applied. The second, `WideState`, changes the [**DisplayMode**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.splitview.displaymode) property of the [**SplitView**](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.splitview) to **Inline** and opens the pane. This state is applied in the SizeChanged event handler if the window width is greater than 640 effective pixels.
136136

137137
> [!NOTE]
138-
> Windows doesn't provide a way for your app to detect the specific device your app is running on. It can tell you the device family (desktop, etc) the app is running on, the effective resolution, and the amount of screen space available to the app (the size of the app's window). We recommend defining visual states for [screen sizes and break points](screen-sizes-and-breakpoints-for-responsive-design.md).
138+
> Windows doesn't provide a way for your app to detect the specific device your app is running on. It can tell you the device family (desktop, etc) the app is running on, the effective resolution, and the amount of screen space available to the app (the size of the app's window). We recommend defining visual states for [screen sizes and break points](../../design/layout/screen-sizes-and-breakpoints-for-responsive-design.md).
139139
140140
```xaml
141141
<Page ...

hub/apps/develop/ui/navigation/navigate-between-two-pages.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ Almost every app requires navigation between pages. Even a simple app with a sin
3333

3434
To create a blank app in Visual Studio:
3535

36-
1. To set up your development computer, see [Start developing Windows apps](../../get-started/start-here.md).
36+
1. To set up your development computer, see [Start developing Windows apps](../../../get-started/start-here.md).
3737
1. From the Microsoft Visual Studio start window, select **Create a new project**, OR, on the Visual Studio menu, choose **File** > **New** > **Project**.
3838
1. In the **Create a new project** dialog's drop-down filters, select **C#** or **C++**, **Windows**, and **WinUI**, respectively.
3939
1. Select the **Blank App, Packaged (WinUI in Desktop)** project template, and click **Next**. That template creates a desktop app with a WinUI-based user interface.
@@ -369,7 +369,7 @@ Now, when you click back to main page, the name you entered in the text box is s
369369

370370
## 6. Customize page transition animations
371371

372-
By default, each page is animated into the frame when navigation occurs. The default animation is an "entrance" animation that causes the page to slide up from the bottom of the window. However, you can choose different animation options that better suit the navigation of your app. For example, you can use a "drill in" animation to give the feeling that the user is going deeper into your app, or a horizontal slide animation to give the feeling that two pages are peers. For more info, see [Page transitions](../motion/page-transitions.md).
372+
By default, each page is animated into the frame when navigation occurs. The default animation is an "entrance" animation that causes the page to slide up from the bottom of the window. However, you can choose different animation options that better suit the navigation of your app. For example, you can use a "drill in" animation to give the feeling that the user is going deeper into your app, or a horizontal slide animation to give the feeling that two pages are peers. For more info, see [Page transitions](../../motion/page-transitions.md).
373373

374374
These animations are represented by sub-classes of [NavigationTransitionInfo](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.media.animation.navigationtransitioninfo). To specify the animation to use for a page transition, you'll use the third overload of the `Navigate` method and pass a `NavigationTransitionInfo` sub-class as the third parameter (`infoOverride`). Here's the signature of this `Navigate` overload:
375375

@@ -460,6 +460,6 @@ Now, when you navigate between pages, the pages slide left and right, which prov
460460

461461
## Related articles
462462

463-
- [Navigation design basics for Windows apps](./navigation-basics.md)
463+
- [Navigation design basics for Windows apps](../../../design/basics/navigation-basics.md)
464464
- [Navigation view](../controls/navigationview.md)
465465
- [Navigation history and backwards navigation](navigation-history-and-backwards-navigation.md)

hub/apps/develop/ui/navigation/navigation-history-and-backwards-navigation.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -26,9 +26,9 @@ To implement backwards navigation in your app, place a back button at the top le
2626
2727
## Back button
2828

29-
We recommend that you place the back button in the upper left corner of your app. If you [customize the title bar](../../develop/title-bar.md), place the back button in the title bar. See [Title bar design > Back button](/windows/apps/design/basics/titlebar-design#back-button) for more info.
29+
We recommend that you place the back button in the upper left corner of your app. If you [customize the title bar](../../title-bar.md), place the back button in the title bar. See [Title bar design > Back button](/windows/apps/design/basics/titlebar-design#back-button) for more info.
3030

31-
If you use the [TitleBar](../controls/title-bar.md) control to create a custom title bar, use the built-in back button. Set [IsBackButtonVisible](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.titlebar.isbackbuttonvisible) to `true`, set [IsBackButtonEnabled](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.titlebar.isbackbuttonenabled) as needed, and handle the [BackRequested](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.titlebar.backrequested) event to navigate.
31+
If you use the [TitleBar](../../controls/title-bar.md)control to create a custom title bar, use the built-in back button. Set [IsBackButtonVisible](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.titlebar.isbackbuttonvisible) to `true`, set [IsBackButtonEnabled](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.titlebar.isbackbuttonenabled) as needed, and handle the [BackRequested](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.titlebar.backrequested) event to navigate.
3232

3333
To create a stand-alone back button, use the [Button](../controls/buttons.md) control with the `TitleBarBackButtonStyle` resource, and place the button at the top left hand corner of your app's UI (for details, see the XAML code examples below).
3434

@@ -174,5 +174,5 @@ winrt::Microsoft::UI::Xaml::Window App::window{ nullptr };
174174

175175
## Related articles
176176

177-
- [Navigation basics](navigation-basics.md)
177+
- [Navigation basics](../../../design/basics/navigation-basics.md)
178178
- [Implement basic navigation](navigate-between-two-pages.md)

hub/apps/develop/ui/shadows.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -32,18 +32,18 @@ Here is how ThemeShadow has been implemented on a MenuFlyout. MenuFlyout has a b
3232

3333
The following common controls will automatically use ThemeShadow to cast shadows from 32px depth unless otherwise specified:
3434

35-
- [Context menu](ui/controls/menus.md), [Command bar](ui/controls/command-bar.md), [Command bar flyout](ui/controls/command-bar-flyout.md), [MenuBar](ui/controls/menus.md#create-a-menu-bar)
36-
- [Dialogs and flyouts](ui/controls/dialogs-and-flyouts/index.md) (Dialog at 128px)
37-
- [NavigationView](ui/controls/navigationview.md)
38-
- [ComboBox](ui/controls/combo-box.md), [DropDownButton, SplitButton, ToggleSplitButton](ui/controls/buttons.md)
39-
- [TeachingTip](ui/controls/dialogs-and-flyouts/teaching-tip.md)
40-
- [AutoSuggestBox](ui/controls/auto-suggest-box.md)
41-
- [Calendar/Date/Time pickers](ui/controls/date-and-time.md)
42-
- [Tooltip](ui/controls/tooltips.md) (16px)
43-
- [Number Box](ui/controls/number-box.md)
44-
- [TabView](ui/controls/tab-view.md)
45-
- [Media transport control](ui/controls/media-playback.md#media-transport-controls), [InkToolbar](ui/controls/inking-controls.md)
46-
- [BreadcrumbBar](ui/controls/breadcrumbbar.md)
35+
- [Context menu](controls/menus.md), [Command bar](controls/command-bar.md), [Command bar flyout](controls/command-bar-flyout.md), [MenuBar](controls/menus.md#create-a-menu-bar)
36+
- [Dialogs and flyouts](controls/dialogs-and-flyouts/index.md) (Dialog at 128px)
37+
- [NavigationView](controls/navigationview.md)
38+
- [ComboBox](controls/combo-box.md), [DropDownButton, SplitButton, ToggleSplitButton](controls/buttons.md)
39+
- [TeachingTip](controls/dialogs-and-flyouts/teaching-tip.md)
40+
- [AutoSuggestBox](controls/auto-suggest-box.md)
41+
- [Calendar/Date/Time pickers](controls/date-and-time.md)
42+
- [Tooltip](controls/tooltips.md) (16px)
43+
- [Number Box](controls/number-box.md)
44+
- [TabView](controls/tab-view.md)
45+
- [Media transport control](controls/media-playback.md#media-transport-controls), [InkToolbar](controls/inking-controls.md)
46+
- [BreadcrumbBar](controls/breadcrumbbar.md)
4747
- [Connected animation](../../design/motion/connected-animation.md)
4848

4949
> [!NOTE]

0 commit comments

Comments
 (0)