We’re utilizing the xamDockManager and within that we’re utilizing the DocumentContentHost and finally the TabGroupPane to host ContentPane. What we’ve found is when we add multiple ContentPanes to the TabGroupPane that 1) that ContentPanes disappear from the viewable area and 2) there is no visual indication to the user that additional screens are viewable. If I compare this to the Windows Forms TabControl 2 arrow buttons appear when additional tabs are available that are not within the viewable area.
Take a look at the attachment to see what Im referring to..
As you can see in the red box that there is no visual indication to the user there are additional windows.
I have looked at the Feature Browser and noticed that no matter now many tabs we put on a window that something does not appear for users to indicate additional tabs / content panes exist. Also, I dont want to add a tab carousel as that does not appear professional...so looking for how to add something to this.
Hello,
Thank you for your post. I have been looking into it and I checked the Feature Browser under XamTabControl / Interacting with the XamTabControl / Add/ Remove Tabs section and when I added a couple of tabs to spin buttons appear, so I was able to scroll left and right. I suggest you see this sample and if it doesn’t help you could please send me an isolated sample project where your issue is reproduced, so I can investigate it further for you.
Looking forward for your reply.
Does this same functionality work with a tabgrouppane as mentioned above? If it is in the featurebrowser - please point to where. Were using the dockmanager with contentpane to show tabgroups.
Hello again,
Also I can say that the current behavior is intentional as it mimics the behavior in Visual Studio and we use a custom panel that is designed to do so. Visual Studio doesn’t show scroll buttons in the document area - they just show a different glyph for the more window drop down on the right hand side of the tab item area, if there are items out of view. Until the feature request is implemented you can work around this by retemplating the TabGroupPane - we have a specific style/template for the element ,when it’s in the DocumentContentHost. You can find the default Styles in C:\Program Files (x86)\Infragistics\NetAdvantage 2011.2\WPF\DefaultStyles\DockManager\DockManagerGeneric.xaml file.
Hope this helps you.
Thank you for your post. I have been looking into it, but I am not completely sure what do you mean by “bind the tabitemex dynamically”, so could you please be more specific what do you want to achieve?
hi,
can u please suggest me that the change what i have to do to bind the tabitemex dynamically from the below code
<Window x:Class="RenamingTabItems.Window1" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" Title="XamTabItem Runtime Renaming" xmlns:igEditors="http://infragistics.com/Editors" xmlns:igWindows="http://infragistics.com/Windows"> <Grid> <igWindows:XamTabControl x:Name="tabControl" Theme="Office2k7Black"> <igWindows:XamTabControl.Resources> <Style x:Key="{x:Type igWindows:TabItemEx}" TargetType="{x:Type igWindows:TabItemEx}"> <Setter Property="Template"> <Setter.Value> <ControlTemplate TargetType="{x:Type igWindows:TabItemEx}"> <Grid SnapsToDevicePixels="true"> <Border Name="Bd" Padding="{TemplateBinding Padding}" BorderBrush="{TemplateBinding BorderBrush}" Background="{TemplateBinding Background}" BorderThickness="1,1,1,0" CornerRadius="3,3,0,0"> <Grid> <!--Substitute the ContentPresenter with a XamTextEditor--> <igEditors:XamTextEditor PreviewMouseLeftButtonDown="tbEdit_PreviewMouseDoubleClick" BorderThickness="0" Background="Transparent" EditModeStarting="tbEdit_EditModeStarting" EditModeEnding="tbEdit_EditModeEnding" Value="{Binding Header, RelativeSource={RelativeSource TemplatedParent}}"/> </Grid> </Border>
</Grid>
</ControlTemplate> </Setter.Value> </Setter> </Style> </igWindows:XamTabControl.Resources>
<igWindows:TabItemEx Header="Home" Content="{Binding Path=Header, RelativeSource={RelativeSource Self}}" /> <igWindows:TabItemEx Header="Insert" Content="{Binding Path=Header, RelativeSource={RelativeSource Self}}" /> <igWindows:TabItemEx Header="Page Layout" Content="{Binding Path=Header, RelativeSource={RelativeSource Self}}" /> <igWindows:TabItemEx Header="References" Content="{Binding Path=Header, RelativeSource={RelativeSource Self}}" /> <igWindows:TabItemEx Header="Mailing" Content="{Binding Path=Header, RelativeSource={RelativeSource Self}}" /> </igWindows:XamTabControl> </Grid></Window>