Conversation
| if (debugConnection) // this will only be set if global debugging is on and tap is active | ||
| { | ||
| TermControl newControl{ settings, debugConnection }; | ||
| TermControl newControl{ *(winrt::get_self<TerminalSettings>(settings)->CreateChild()), debugConnection }; |
There was a problem hiding this comment.
This change doesn't affect the settings reload bug but I figured we should update this call as well
There was a problem hiding this comment.
It actually will impact reload, if the pane is a debug tap pane :D
| } | ||
|
|
||
| TermControl newControl{ controlSettings, controlConnection }; | ||
| TermControl newControl{ *(winrt::get_self<TerminalSettings>(controlSettings)->CreateChild()), controlConnection }; |
There was a problem hiding this comment.
Oh gosh. Can you file a Code Health task to clean up all the different places in which we create a TerminalControl with its settings? I don't love that we had to make this fix in multiple places.
|
I think you meant to close #9280? |
Yes... thank you for the catch |
|
Hello @PankajBhojwani! Because this pull request has the Do note that I've been instructed to only help merge pull requests of this repository that have been opened for at least 8 hours, a condition that will be fulfilled in about 6 hours 13 minutes. No worries though, I will be back when the time is right! 😉 p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
Summary of the Pull Request
Fix for #9280
In #8602, we started passing a child of the
TerminalSettingsto the control upon tab initialization, but forgot to do the same when new controls get created on a pane split.PR Checklist
Validation Steps Performed
Settings reload with multiple panes works