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

[PR #9091] [MERGED] Teach the renderer to keep thread alive if engine requests it #27410

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

📋 Pull Request Information

Original PR: https://github.com/microsoft/terminal/pull/9091
Author: @miniksa
Created: 2/10/2021
Status: ✅ Merged
Merged: 2/10/2021
Merged by: @DHowett

Base: main ← Head: dev/miniksa/tick

📝 Commits (4)

  • ae9353c Make renderer base tell the thread to tick again if an engine reports that it wants it so continuous draw shaders can keep drawing.
  • b8a3b32 oh... use the actual name of the function that says if we have a shader or not.
  • 486aed0 Disable the continuous redraw for in-built retro effect since it doesn't use time.
  • 94e3492 Code format!

📊 Changes

6 files changed (+45 additions, -0 deletions)

View changed files

📝 src/renderer/base/RenderEngineBase.cpp (+10 -0)
📝 src/renderer/base/renderer.cpp (+8 -0)
📝 src/renderer/dx/DxRenderer.cpp (+22 -0)
📝 src/renderer/dx/DxRenderer.hpp (+2 -0)
📝 src/renderer/inc/IRenderEngine.hpp (+1 -0)
📝 src/renderer/inc/RenderEngineBase.hpp (+2 -0)

📄 Description

Teaches renderer base to keep thread alive if engine requests it.
DxEngine now requests it if shaders are on.

  • The render engine interface now has a true/false to return whether the
    specific renderer wants another frame to immediately follow up. The
    renderer base will ask for this information as it ends the paint on
    any particular engine (which is the time where invalid regions are
    typically cleaned up) and just poke the render thread the same as if
    an invalidation request came in from outside of render-land. That will
    trigger the render thread to just keep moving in the same way as any
    other invalidation.

Validation Steps Performed

  • Actually built it
  • Actually try it

I promised this in #8994

🔄 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/9091 **Author:** [@miniksa](https://github.com/miniksa) **Created:** 2/10/2021 **Status:** ✅ Merged **Merged:** 2/10/2021 **Merged by:** [@DHowett](https://github.com/DHowett) **Base:** `main` ← **Head:** `dev/miniksa/tick` --- ### 📝 Commits (4) - [`ae9353c`](https://github.com/microsoft/terminal/commit/ae9353c53f525a3d0092ae2cf73eedcc701cbb58) Make renderer base tell the thread to tick again if an engine reports that it wants it so continuous draw shaders can keep drawing. - [`b8a3b32`](https://github.com/microsoft/terminal/commit/b8a3b3272accee1a19d69af22665cd47cf7ff866) oh... use the actual name of the function that says if we have a shader or not. - [`486aed0`](https://github.com/microsoft/terminal/commit/486aed0fe9264ebf0c3225efaa9ba93302ef5673) Disable the continuous redraw for in-built retro effect since it doesn't use time. - [`94e3492`](https://github.com/microsoft/terminal/commit/94e3492ce29c3c23676c78bb6045c145ac0440ec) Code format! ### 📊 Changes **6 files changed** (+45 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `src/renderer/base/RenderEngineBase.cpp` (+10 -0) 📝 `src/renderer/base/renderer.cpp` (+8 -0) 📝 `src/renderer/dx/DxRenderer.cpp` (+22 -0) 📝 `src/renderer/dx/DxRenderer.hpp` (+2 -0) 📝 `src/renderer/inc/IRenderEngine.hpp` (+1 -0) 📝 `src/renderer/inc/RenderEngineBase.hpp` (+2 -0) </details> ### 📄 Description Teaches renderer base to keep thread alive if engine requests it. `DxEngine` now requests it if shaders are on. - The render engine interface now has a true/false to return whether the specific renderer wants another frame to immediately follow up. The renderer base will ask for this information as it ends the paint on any particular engine (which is the time where invalid regions are typically cleaned up) and just poke the render thread the same as if an invalidation request came in from outside of render-land. That will trigger the render thread to just keep moving in the same way as any other invalidation. ## Validation Steps Performed - [x] Actually built it - [x] Actually try it I promised this in #8994 --- <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:49 +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#27410
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?