starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

[PR #8962] [MERGED] Added some example images for the pixel shader feature #27351

New Issue
Open
opened 2026-01-31 09:21:29 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 09:21:29 +00:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/microsoft/terminal/pull/8962
Author: @CyberMobius
Created: 1/30/2021
Status: ✅ Merged
Merged: 2/1/2021
Merged by: @DHowett

Base: main ← Head: feature/PixelShaderExampleImages

📝 Commits (1)

  • dd8345a Added some example images for the pixel shader feature

📊 Changes

5 files changed (+13 additions, -1 deletions)

View changed files

📝 samples/PixelShaders/README.md (+13 -1)
➕ samples/PixelShaders/Screenshots/TerminalDefault.PNG (+0 -0)
➕ samples/PixelShaders/Screenshots/TerminalInvert.PNG (+0 -0)
➕ samples/PixelShaders/Screenshots/TerminalRasterbars.PNG (+0 -0)
➕ samples/PixelShaders/Screenshots/TerminalRetro.PNG (+0 -0)

📄 Description

I added some sample screenshots on the README for the pixel shader feature

Fixes #8960

Detailed Description of the Pull Request / Additional comments

I created 4 screenshots using preview windows terminal, one for the default look, and three for the shaders mentioned in the readme.

For the first shader, Invert.hlsl, I put it in a table and placed a screenshot of the default next to it. I don't think it would be clear what the shader did without being able to compare it against the default.

For Rasterbars.hlsl I put a screenshot right after the code sample for it. I added a screenshot for Retro.hlsl just before the last sentence

I also created a folder named Screenshots in terminal/samples/Pixelshaders to hold all of the screenshots.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/microsoft/terminal/pull/8962 **Author:** [@CyberMobius](https://github.com/CyberMobius) **Created:** 1/30/2021 **Status:** ✅ Merged **Merged:** 2/1/2021 **Merged by:** [@DHowett](https://github.com/DHowett) **Base:** `main` ← **Head:** `feature/PixelShaderExampleImages` --- ### 📝 Commits (1) - [`dd8345a`](https://github.com/microsoft/terminal/commit/dd8345addfa1cad051a0e78529ee0e2105059b81) Added some example images for the pixel shader feature ### 📊 Changes **5 files changed** (+13 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `samples/PixelShaders/README.md` (+13 -1) ➕ `samples/PixelShaders/Screenshots/TerminalDefault.PNG` (+0 -0) ➕ `samples/PixelShaders/Screenshots/TerminalInvert.PNG` (+0 -0) ➕ `samples/PixelShaders/Screenshots/TerminalRasterbars.PNG` (+0 -0) ➕ `samples/PixelShaders/Screenshots/TerminalRetro.PNG` (+0 -0) </details> ### 📄 Description I added some sample screenshots on the README for the pixel shader feature Fixes #8960 ## Detailed Description of the Pull Request / Additional comments I created 4 screenshots using preview windows terminal, one for the default look, and three for the shaders mentioned in the readme. For the first shader, `Invert.hlsl`, I put it in a table and placed a screenshot of the default next to it. I don't think it would be clear what the shader did without being able to compare it against the default. For `Rasterbars.hlsl` I put a screenshot right after the code sample for it. I added a screenshot for `Retro.hlsl` just before the last sentence I also created a folder named Screenshots in `terminal/samples/Pixelshaders` to hold all of the screenshots. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
claunia added the pull-request label 2026-01-31 09:21:29 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#27351
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?