terminal/src/cascadia/TerminalControl/TSFInputControl.xaml

<UserControl
    x:Class="Microsoft.Terminal.Control.TSFInputControl"
    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
    xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
    xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
    mc:Ignorable="d"
    d:DesignHeight="768"
    d:DesignWidth="1024">

    <Canvas x:Name="Canvas"
            Visibility="Collapsed">
        <TextBlock x:Name="TextBlock"
                   IsTextSelectionEnabled="false"
                   TextWrapping="Wrap"
                   TextDecorations="Underline" />
    </Canvas>
</UserControl>
Replace TSFInputControl with a xaml file (#4743) This pull request is like #4729 but for TSFInputControl. 2020-02-28 20:32:19 +01:00			`<UserControl`
Rename `Microsoft.Terminal.TerminalControl` to `.Control`; Split into dll & lib (#9472) BE NOT AFRAID. I know that there's 107 files in this PR, but almost all of it is just find/replacing `TerminalControl` with `Control`. This is the start of the work to move TermControl into multiple pieces, for #5000. The PR starts this work by: * Splits `TerminalControl` into separate lib and dll projects. We'll want control tests in the future, and for that, we'll need a lib. * Moves `ICoreSettings` back into the `Microsoft.Terminal.Core` namespace. We'll have other types in there soon too. * I could not tell you why this works suddenly. New VS versions? New cppwinrt version? Maybe we're just better at dealing with mdmerge bugs these days. * RENAMES `Microsoft.Terminal.TerminalControl` to `Microsoft.Terminal.Control`. This touches pretty much every file in the sln. Sorry about that (not sorry). An upcoming PR will move much of the logic in TermControl into a new `ControlCore` class that we'll add in `Microsoft.Terminal.Core`. `ControlCore` will then be unittest-able in the `UnitTests_TerminalCore`, which will help prevent regressions like #9455 ## Detailed Description of the Pull Request / Additional comments You're really gonna want to clean the sln first, then merge this into your branch, then rebuild. It's very likely that old winmds will get left behind. If you see something like ``` Error MDM2007 Cannot create type Microsoft.Terminal.TerminalControl.KeyModifiers in read-only metadata file Microsoft.Terminal.TerminalControl. ``` then that's what happened to you. 2021-03-17 21:47:24 +01:00			`x:Class="Microsoft.Terminal.Control.TSFInputControl"`
Replace TSFInputControl with a xaml file (#4743) This pull request is like #4729 but for TSFInputControl. 2020-02-28 20:32:19 +01:00			`xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"`
			`xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"`
			`xmlns:d="http://schemas.microsoft.com/expression/blend/2008"`
			`xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"`
			`mc:Ignorable="d"`
			`d:DesignHeight="768"`
			`d:DesignWidth="1024">`

Polish AutomationProperties and UIA Tree Navigation (#4805) AutomationProperties of interest in this PR include... - Name: the name of a UI element (generally used as the main identifier for it) - HelpText: an additional description for a more complex UI element - AccessibilityView[1] - Raw: hide from the UIA tree. Only navigate to this if you know what you're doing - Control: a control without any content in it. Basically, a point at which the user can make a decision as to how to navigate the tree or invoke an action. - Content: a control that also has content to present to the user. I set a few more AutomationProperties throughout Windows Terminal... - MinMaxClose Control: hidden (we can/should rely on the true buttons that we are hiding) - SplitButton: Name and Help text (currently ignored due to #4804, but having it in the resource file won't cause any problems) - SearchBox: added a more specific name to the close button - BackgroundImage: hide it ## References A few additional work items have been created for tracking... - SplitButton: https://github.com/microsoft/terminal/issues/4804 ## PR Checklist * [X] Closes #2099 * [X] Closes #2102 ## Validation Steps Performed Verified using Accessibility Insights and Inspect.exe [1] https://docs.microsoft.com/en-us/windows/win32/winauto/uiauto-treeoverview 2020-03-05 23:32:46 +01:00			`<Canvas x:Name="Canvas"`
			`Visibility="Collapsed">`
Replace TSFInputControl with a xaml file (#4743) This pull request is like #4729 but for TSFInputControl. 2020-02-28 20:32:19 +01:00			`<TextBlock x:Name="TextBlock"`
			`IsTextSelectionEnabled="false"`
Allow IME Text Wrapping (#5005) ## Summary of the Pull Request This PR turns on TextWrapping on `TSFInputControl::TextBlock`. Once the TextBlock hits the end of the Terminal window, it will wrap downwards, but the TextBlock will have as much width as it had when composition started. Unfortunately, this means if composition starts right at the end of the Terminal with enough width for just one character, there will be a vertical line of characters down the right side of the Terminal 😅. It's definitely not ideal, and I imagine this won't be the last time we visit this issue, but for now users can see what they're typing. ## PR Checklist * [x] Closes #3657 * [x] CLA signed. If not, go over [here](https://cla.opensource.microsoft.com/microsoft/Terminal) and sign the CLA * [x] Tests added/passed ## Validation Steps Performed Played around with IME towards the edge of the Terminal window. 2020-03-19 20:15:13 +01:00			`TextWrapping="Wrap"`
Replace TSFInputControl with a xaml file (#4743) This pull request is like #4729 but for TSFInputControl. 2020-02-28 20:32:19 +01:00			`TextDecorations="Underline" />`
			`</Canvas>`
			`</UserControl>`