https://stackoverflow.com/questions/19857489
italiano
english
français
española
中国
日本の
العربية
Deutsch
한국어
Português
Russian
Ok... this is why you should always show us what your overall goal is. Had I not asked that, then you might not have got an answer because you were initially looking in the wrong place. Right, lecture over, on to the answer.
As it is, it's nice and simple... we don't need to handle any events, we can just use a Trigger in the ScrollViewer.Style. Just add this to your ScrollViewer (making sure that you remove your ScrollBar properties from the ScrollViewer definition):
<ScrollViewer x:Name="ScrollViewer">
...
<ScrollViewer.Style>
<Style>
<Setter Property="ScrollViewer.HorizontalScrollBarVisibility"
Value="Disabled" />
<Setter Property="ScrollViewer.VerticalScrollBarVisibility"
Value="Disabled" />
<Style.Triggers>
<Trigger Property="UIElement.IsMouseOver" Value="True">
<Setter Property="ScrollViewer.HorizontalScrollBarVisibility"
Value="Visible" />
<Setter Property="ScrollViewer.VerticalScrollBarVisibility"
Value="Visible" />
</Trigger>
</Style.Triggers>
</Style>
</ScrollViewer.Style>
</ScrollViewer>
UPDATE >>>
Ok, I finally fully understand your question now... sorry for being so slow. However, you have a real problem here because this is not an error, it is the designed behaviour. This is because the TabItem controls are inside the ScrollViewer control, so moving the mouse over them is the same as moving them over the ScrollViewer.
If I were trying to implement your requirements, I would abandon the TabControl altogether and just use RadioButton controls that load views into the lower area instead. You could even style your RadioButtons to look like tabs if you wanted.
UPDATE 2 >>>
Well that's a long story with several parts. I don't have time to type the whole thing out here, but I'll talk you through it briefly. First you'll have to create a new ControlTemplate for the RadioButtons and you can put them in a StackPanel with its Orientation property set to True, then put that in your ScrollViewer.
Next, you'll need to define an enum with one value for each 'tab' or view and an EnumToBoolConverter... I found a good example for you in the How to bind RadioButtons to an enum? post.
The next job is to create the 'tab item content' area. For this you'll need a ContentControl to display each view, or tab item content. The idea is that you have an abstract BaseViewModel class that implements the INotifyPropertyChanged interface and a class that extends this base class for each tab that you want to display. Each class will provide all of the data properties and functionality that the related view, or tab requires.
Because they all extend the base class, you can have a property of that type that you can set to each of the extended view models. This is where the ContentControl comes into play, as it binds to the BaseViewModel property.
The final part is to define a DataTemplate for each view model class that simply displays the related view. Then when the various RadioButtons are selected, you can just set the BaseViewModel property to the relevant view model which will result in the paired view being displayed. You can see a fuller explanation with code examples in my answer to the WPF MVVM navigate views post.
