Windows Terminal 이전 버전 및 전체 버전

This release of Windows Terminal addresses a crash in self-elevation.

Huge thanks to @jboelter for fixing it in 1.17 (#14637).

Changes
• The refreshed Windows 11 UI from the 1.13 preview builds is now available in 1.12!

Bug Fixes
Appearance
• Our Maximize/Restore button is now a fine round boi

Accessibility
• The profile list in the Settings UI now offers tooltips for long profile names
• We'll automatically focus the window renamer textbox when it opens
• High contrast will no longer result in a ridiculous and bad titlebar color
• When you delete a color scheme, we'll move focus back to the color scheme list
• When you delete a profile, we will re-focus the delete button automatically
• Two instances of huge debug log spam with a screen reader connected have been stamped out

Usability
• We've added some text to the color schemes page indicating that it is for editing--not setting--color schemes
• We're working to refine how color schemes are set and edited, so stay tuned for future improvements!
• The retro terminal effect (as well as other shaders) will now work on pre-D3D11 hardware!
• Terminal will once again render properly when you move between different-DPI displays
• Resizing the window while a background color or underline is displayed will no longer smear it across the whole screen plus a fix for a huge crash that PR introduced
• It took us three releases to get it right, but we've finally solved the issue where we'd punch a hole straight through the Terminal when a dialog appeared

Reliability
• Typing an invalid background image path into the Settings UI will no longer send Terminal to a farm upstate
• There was an issue on Windows 11 where Terminal would queue up billions of animations while the screen was off; it will now no longer do so
• We've fixed crashes in ProposeCommandline, Monarch::_GetPID and other parts of WT's RPC infrastructure
• On Windows 10, the settings UI will no longer sometimes crash on close (we've updated to a new build of WinUI 2 for the fix!)

Miscellaneous
• Windows will no longer reject certain Terminal updates/reinstalls due to "differing package content"
• Fragments can once again override the names of generated profiles
• An issue from the 1073 series, where you could not upgrade the bundle using DISM, has been resolved
• As a result, our bundle version is now over three thousand!
• @dmezh contributed some wording changes to the text about transparency/opacity

Changes
• The refreshed Windows 11 UI from the 1.13 preview builds is now available in 1.12!

Bug Fixes
Appearance
• Our Maximize/Restore button is now a fine round boi

Accessibility
• The profile list in the Settings UI now offers tooltips for long profile names
• We'll automatically focus the window renamer textbox when it opens
• High contrast will no longer result in a ridiculous and bad titlebar color
• When you delete a color scheme, we'll move focus back to the color scheme list
• When you delete a profile, we will re-focus the delete button automatically
• Two instances of huge debug log spam with a screen reader connected have been stamped out

Usability
• We've added some text to the color schemes page indicating that it is for editing--not setting--color schemes
• We're working to refine how color schemes are set and edited, so stay tuned for future improvements!
• The retro terminal effect (as well as other shaders) will now work on pre-D3D11 hardware!
• Terminal will once again render properly when you move between different-DPI displays
• Resizing the window while a background color or underline is displayed will no longer smear it across the whole screen plus a fix for a huge crash that PR introduced
• It took us three releases to get it right, but we've finally solved the issue where we'd punch a hole straight through the Terminal when a dialog appeared

Reliability
• Typing an invalid background image path into the Settings UI will no longer send Terminal to a farm upstate
• There was an issue on Windows 11 where Terminal would queue up billions of animations while the screen was off; it will now no longer do so
• We've fixed crashes in ProposeCommandline, Monarch::_GetPID and other parts of WT's RPC infrastructure
• On Windows 10, the settings UI will no longer sometimes crash on close (we've updated to a new build of WinUI 2 for the fix!)

Miscellaneous
• Windows will no longer reject certain Terminal updates/reinstalls due to "differing package content"
• Fragments can once again override the names of generated profiles
• An issue from the 1073 series, where you could not upgrade the bundle using DISM, has been resolved
• As a result, our bundle version is now over three thousand!
• @dmezh contributed some wording changes to the text about transparency/opacity

Changes
This version of Windows Terminal is now distributed in two bundles, one of which works on Windows 10-11 and the
other of which only works on Windows 11. The Windows 11 version is much smaller because we no longer need to work around
a platform issue related to our dependencies.

If you intend on using Terminal as an unpackaged application--that is, extracting the msix file--we recommend that
you use the Win10 bundle. You will need the Visual C++ runtime redistributable.

In addition, if you install the packaged version on either Windows 10 or Windows 11, it now depends on the Visual C++ Universal Runtime Package.

Despite these distributions having different version numbers, they are built from the same code and there is no
functional difference between them.

If you install the Windows 10 verison on Windows 11, it will probably automatically upgrade itself to the Windows 11
version. It turns out that it is impossible to have two bundles with the same version number, so it has to be this
way.

Bug Fixes
- Usability
• Terminal can once again be configured as a startup application, and can be detected by tools like PowerToys (#12491)
• There was a puzzling "Element not found" error during settings loading; there is no longer such an error (#12687)
• Terminal will no longer mix up profiles when it is launched in response to a console application spawning (#12484)
• Formatted copy will now try harder to preserve Unicode charatcers in RTF (#12586) (thanks @ianjoneill!)
• We have replaced the word "Summon" with "Show/Hide" in the command palette for improved localization (#12603)
• Our confidence in the settings UI's Save button has led to us no longer backing up the settings JSON file (#12652)
• We won't be deleting the 61,000 backups we did leave on your hard drive, but what's a couple thousand kilobytes between friends?

- Accessibility
• Terminal now announces newly-printed text to any attached screen reader (#12358)
• Command palette search now tries to announce the number of results to the screen reader (#12429)

- Reliability
• We won't crash any longer if you give us a command line that is a directory (#12538) (thanks @ianjoneill!)
• A crash on launch related to multi-windowing and the default terminal setting has been quashed (subset of #12205)
• Fixed a crash setting the hotkey during teardown (#12580)
• Fixed a different pair of crashes, also likely related to default terminal handoff (#12666)
• ScrollConsoleScreenBuffer no longer takes the console upstate (#12669)
• Pressing Page Up or Page Down with an empty command palette, which seemed like a reasonable thing to do, was taught to not crash the Terminal (#12528)

- Rendering
• Font axes/features once again work across a DPI change (#12492)

Changes
This version of Windows Terminal is now distributed in two bundles, one of which works on Windows 10-11 and the
other of which only works on Windows 11. The Windows 11 version is much smaller because we no longer need to work around
a platform issue related to our dependencies.

If you intend on using Terminal as an unpackaged application--that is, extracting the msix file--we recommend that
you use the Win10 bundle. You will need the Visual C++ runtime redistributable.

In addition, if you install the packaged version on either Windows 10 or Windows 11, it now depends on the Visual C++ Universal Runtime Package.

Despite these distributions having different version numbers, they are built from the same code and there is no
functional difference between them.

If you install the Windows 10 verison on Windows 11, it will probably automatically upgrade itself to the Windows 11
version. It turns out that it is impossible to have two bundles with the same version number, so it has to be this
way.

Bug Fixes
- Usability
• Terminal can once again be configured as a startup application, and can be detected by tools like PowerToys (#12491)
• There was a puzzling "Element not found" error during settings loading; there is no longer such an error (#12687)
• Terminal will no longer mix up profiles when it is launched in response to a console application spawning (#12484)
• Formatted copy will now try harder to preserve Unicode charatcers in RTF (#12586) (thanks @ianjoneill!)
• We have replaced the word "Summon" with "Show/Hide" in the command palette for improved localization (#12603)
• Our confidence in the settings UI's Save button has led to us no longer backing up the settings JSON file (#12652)
• We won't be deleting the 61,000 backups we did leave on your hard drive, but what's a couple thousand kilobytes between friends?

- Accessibility
• Terminal now announces newly-printed text to any attached screen reader (#12358)
• Command palette search now tries to announce the number of results to the screen reader (#12429)

- Reliability
• We won't crash any longer if you give us a command line that is a directory (#12538) (thanks @ianjoneill!)
• A crash on launch related to multi-windowing and the default terminal setting has been quashed (subset of #12205)
• Fixed a crash setting the hotkey during teardown (#12580)
• Fixed a different pair of crashes, also likely related to default terminal handoff (#12666)
• ScrollConsoleScreenBuffer no longer takes the console upstate (#12669)
• Pressing Page Up or Page Down with an empty command palette, which seemed like a reasonable thing to do, was taught to not crash the Terminal (#12528)

- Rendering
• Font axes/features once again work across a DPI change (#12492)