Change tab Title fontsize / color

Hello,

Based on the above I assume you mean you want to change what is in a tabbed MDI document tab.  You could change the TabbedMdiHost.TabItemContainerStyle property.  Its default value is:

<Style TargetType="docking:AdvancedTabItem">
	<Setter Property="Header" Value="{Binding TabTextResolved}" />
	<Setter Property="HeaderTemplate">
		<Setter.Value>
			<DataTemplate>
				<TextBlock Text="{Binding Converter={StaticResource TitleConverter}}" TextTrimming="None" TextWrapping="NoWrap" VerticalAlignment="Center" />
			</DataTemplate>
		</Setter.Value>
	</Setter>
</Style>

Hi,

I try this and a lot of others but I can't change Title Font Size/Color, ...., for a DocumentWindow

U says that I need change "TabbedMdiHost.TabItemContainerStyle" but you target "docking:AdvancedTabItem"

Do u have a little sample ?

 thanks

Hello,

The above style is correct and you just need to set it to the TabItemContainerStyle property of the TabbedMdiHost in your XAML.  Tab items are rendered via AdvancedTabItem controls.  Then you can change the content of that DataTemplate to whatever you need.  It could use a different font size or even something other than a TextBlock control.

I've tried your above suggestion, and still cannot seem to create a custom AdvancedTabItem header in a docking window.  Any other thoughts?

Thanks,

Brian

<Window
        xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
        xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
        xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
        xmlns:local="clr-namespace:AdvancedTabStyle"
        xmlns:docking="http://schemas.actiprosoftware.com/winfx/xaml/docking"
      	xmlns:dockingThemes="http://schemas.actiprosoftware.com/winfx/xaml/themes"
        xmlns:shared="http://schemas.actiprosoftware.com/winfx/xaml/shared" x:Class="AdvancedTabStyle.MainWindow"
        mc:Ignorable="d"
        Title="MainWindow" Height="350" Width="525">
  <Window.Resources>
    <Style TargetType="docking:AdvancedTabItem" x:Key="mystyle">
      <Setter Property="Header" Value="{Binding TabTextResolved}" />
      <Setter Property="Background" Value="Orange"/>
      <Setter Property="HeaderTemplate">
        <Setter.Value>
          <DataTemplate>
            <TextBlock Text="YO YO YO!  My Personal header!" TextTrimming="None" TextWrapping="NoWrap" VerticalAlignment="Center" />
          </DataTemplate>
        </Setter.Value>
      </Setter>
    </Style>
  </Window.Resources>
  <Grid>
    <docking:DockSite>
      <docking:SplitContainer>
        <docking:ToolWindowContainer>
          <docking:ToolWindow Title="Test1"/>
          <docking:ToolWindow Title="Test1"/>
        </docking:ToolWindowContainer>

        <docking:SplitContainer>
          <docking:Workspace>
            <docking:TabbedMdiHost  >
              <docking:TabbedMdiContainer TabItemContainerStyle="{StaticResource mystyle}"  >
                <docking:DocumentWindow Title="DocWindow" FileName="C:\code\audiohtml.htm"/>
                <docking:DocumentWindow Title="DocWindow2" FileName="C:\code\audiohtml.htm"/>
              </docking:TabbedMdiContainer>
            </docking:TabbedMdiHost>
          </docking:Workspace>
        </docking:SplitContainer>
      </docking:SplitContainer>
    </docking:DockSite>
  </Grid>
</Window>

Crap.  As usual, I figured it out as soon as I posted it.  The TabitemContiainerStyle is on the TabbedMdiHost, not the TabbedMdiContainer.  Pretty confusing, but here is what was working for me:

<Window
        xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
        xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
        xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
        xmlns:local="clr-namespace:AdvancedTabStyle"
        xmlns:docking="http://schemas.actiprosoftware.com/winfx/xaml/docking"
      	xmlns:dockingThemes="http://schemas.actiprosoftware.com/winfx/xaml/themes"
        xmlns:shared="http://schemas.actiprosoftware.com/winfx/xaml/shared" x:Class="AdvancedTabStyle.MainWindow"
        mc:Ignorable="d"
        Title="MainWindow" Height="350" Width="525">
  <Window.Resources>
    <Style TargetType="docking:AdvancedTabItem" x:Key="mystyle">
      <Setter Property="Header" Value="{Binding TabTextResolved}" />
      <Setter Property="Background" Value="Orange"/>
      <Setter Property="HeaderTemplate">
        <Setter.Value>
          <DataTemplate>
            <TextBlock Text="YO YO YO!  My Personal header!" TextTrimming="None" TextWrapping="NoWrap" VerticalAlignment="Center" />
          </DataTemplate>
        </Setter.Value>
      </Setter>
    </Style>
  </Window.Resources>
  <Grid>
    <docking:DockSite>
      <docking:SplitContainer>
        <docking:ToolWindowContainer>
          <docking:ToolWindow Title="Test1"/>
          <docking:ToolWindow Title="Test1"/>
        </docking:ToolWindowContainer>

        <docking:SplitContainer>
          <docking:Workspace>
            <docking:TabbedMdiHost  TabItemContainerStyle="{StaticResource mystyle}" >
              <docking:TabbedMdiContainer  >
                <docking:DocumentWindow Title="DocWindow" FileName="C:\code\audiohtml.htm"/>
                <docking:DocumentWindow Title="DocWindow2" FileName="C:\code\audiohtml.htm"/>
              </docking:TabbedMdiContainer>
            </docking:TabbedMdiHost>
          </docking:Workspace>
        </docking:SplitContainer>
      </docking:SplitContainer>
    </docking:DockSite>
  </Grid>
</Window>

Hi Brian,

Yes, the reason for that is that container instances are transient and are created/destroyed as needed when layout changes occur.  You should never directly reference or set properties directly on any container class (like ToolWindowContainer).  The reason the property is on TabbedMdiHost is that control is always present in the layout and doesn't change with layout changes.  So it's an anchor point so to speak that you can set properties on, and they are set up internally to publish out to all the containers that are within the host.  That's why it works that way.