Bind TabHeaderControl to TerminalTab properties #12413

Closed
opened 2026-01-31 03:15:02 +00:00 by claunia · 5 comments
Owner

Originally created by @Don-Vito on GitHub (Feb 5, 2021).

Description of the new feature/enhancement

As a part of https://github.com/microsoft/terminal/pull/9041 we are adding indicators (like progress value) to the terminal tab (so it can be rendered in different places).

Currently the TabHeaderControl is updated manually in the code behind.
Instead we could bind the TabHeaderControl to the properties upon initialization.

Originally created by @Don-Vito on GitHub (Feb 5, 2021). # Description of the new feature/enhancement As a part of https://github.com/microsoft/terminal/pull/9041 we are adding indicators (like progress value) to the terminal tab (so it can be rendered in different places). Currently the `TabHeaderControl` is updated manually in the code behind. Instead we could bind the `TabHeaderControl` to the properties upon initialization.
Author
Owner

@zadjii-msft commented on GitHub (Feb 8, 2021):

Yea I agree with doing this as a follow up. Thanks for filing!

@zadjii-msft commented on GitHub (Feb 8, 2021): Yea I agree with doing this as a follow up. Thanks for filing!
Author
Owner

@zadjii-msft commented on GitHub (Feb 8, 2021):

I'm just gonna mention this here so it's not lost from my review on #9041.

Almost seems like there should be a common interface for both TabPaletteItem and TabHeaderControl, so whenever we add a property to one of them, it automatically needs to be implemented in the other too (even if just to no-op it)

@zadjii-msft commented on GitHub (Feb 8, 2021): I'm just gonna mention this here so it's not lost from my review on #9041. > Almost seems like there should be a common interface for both `TabPaletteItem` and `TabHeaderControl`, so whenever we add a property to one of them, it automatically needs to be implemented in the other too (even if just to no-op it)
Author
Owner

@DHowett commented on GitHub (Feb 12, 2021):

@Don-Vito I think your tab header thing actually made this better. Should we close?

@DHowett commented on GitHub (Feb 12, 2021): @Don-Vito I think your tab header thing actually made this better. Should we close?
Author
Owner

@Don-Vito commented on GitHub (Feb 12, 2021):

@Don-Vito I think your tab header thing actually made this better. Should we close?

I think we should close, as long as we don't plan to make this control reusable. Which I guess is not the case.

@Don-Vito commented on GitHub (Feb 12, 2021): > @Don-Vito I think your tab header thing actually made this better. Should we close? I think we should close, as long as we don't plan to make this control reusable. Which I guess is not the case.
Author
Owner

@zadjii-msft commented on GitHub (Feb 12, 2021):

Okay yea, I doubt anyone's going to be re-using that control any time soon. We can revisit if that ever changes.

@zadjii-msft commented on GitHub (Feb 12, 2021): Okay yea, I doubt anyone's going to be re-using that control any time soon. We can revisit if that ever changes.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#12413