@ikeas68 Oh yeah, very old, the problem should definitiv be fixed in v2.
Here is the one for v1.6.5
Here is the one for v1.6.5
<Style x:Key="MetroListView" TargetType="{x:Type ListView}">
<Setter Property="AlternationCount" Value="2" />
<Setter Property="Background" Value="{DynamicResource WhiteBrush}" />
<Setter Property="BorderBrush" Value="{DynamicResource BlackBrush}" />
<Setter Property="BorderThickness" Value="0" />
<Setter Property="OverridesDefaultStyle" Value="True" />
<Setter Property="ScrollViewer.CanContentScroll" Value="False" />
<Setter Property="ScrollViewer.HorizontalScrollBarVisibility" Value="Auto" />
<Setter Property="ScrollViewer.VerticalScrollBarVisibility" Value="Auto" />
<Setter Property="SnapsToDevicePixels" Value="True" />
<Setter Property="Template">
<Setter.Value>
<ControlTemplate TargetType="ListView">
<Border x:Name="Border"
Background="{TemplateBinding Background}"
BorderBrush="{TemplateBinding BorderBrush}"
BorderThickness="{TemplateBinding BorderThickness}"
CornerRadius="{TemplateBinding mah:ControlsHelper.CornerRadius}"
SnapsToDevicePixels="{TemplateBinding SnapsToDevicePixels}">
<ScrollViewer Padding="{TemplateBinding Padding}"
CanContentScroll="{TemplateBinding ScrollViewer.CanContentScroll}"
Focusable="False"
HorizontalScrollBarVisibility="{TemplateBinding ScrollViewer.HorizontalScrollBarVisibility}"
SnapsToDevicePixels="{TemplateBinding SnapsToDevicePixels}"
Style="{DynamicResource MetroGridViewScrollViewerStyle}"
VerticalScrollBarVisibility="{TemplateBinding ScrollViewer.VerticalScrollBarVisibility}">
<ItemsPresenter SnapsToDevicePixels="{TemplateBinding SnapsToDevicePixels}" />
</ScrollViewer>
</Border>
<ControlTemplate.Triggers>
<MultiTrigger>
<MultiTrigger.Conditions>
<Condition Property="IsGrouping" Value="true" />
<Condition Property="VirtualizingPanel.IsVirtualizingWhenGrouping" Value="false" />
</MultiTrigger.Conditions>
<Setter Property="ScrollViewer.CanContentScroll" Value="false" />
</MultiTrigger>
<Trigger Property="IsEnabled" Value="False">
<Setter TargetName="Border" Property="BorderBrush" Value="{DynamicResource GrayBrush9}" />
</Trigger>
</ControlTemplate.Triggers>
</ControlTemplate>
</Setter.Value>
</Setter>
<Setter Property="VerticalContentAlignment" Value="Center" />
</Style>
<Style x:Key="VirtualisedMetroListView"
BasedOn="{StaticResource MetroListView}"
TargetType="{x:Type ListView}">
<Setter Property="ScrollViewer.CanContentScroll" Value="True" />
<Setter Property="ScrollViewer.IsDeferredScrollingEnabled" Value="True" />
<Setter Property="VirtualizingStackPanel.IsVirtualizing" Value="True" />
<Setter Property="VirtualizingStackPanel.IsVirtualizingWhenGrouping" Value="True" />
<Setter Property="VirtualizingStackPanel.VirtualizationMode" Value="Recycling" />
</Style>
metrodialogsettings doenst have any property for foreground color
@punker76,
The way how I launch childwindows is below.
The question is how to stop time update when window is already appeared on the screen.
in other words, I have time of window appearance, but it constantly updates with system time.
How do I "freeze" time of appearance at window title?
The way how I launch childwindows is below.
The question is how to stop time update when window is already appeared on the screen.
in other words, I have time of window appearance, but it constantly updates with system time.
How do I "freeze" time of appearance at window title?
private async void Diag_btn_Click(object sender, RoutedEventArgs e)
{
DiagWindow diagwindow = new DiagWindow() { IsModal = false, AllowMove = true, IsOpen = false };
if (!diagwindow.IsOpen)
diagwindow.Title = $"diagnostics- {DateTime.Now.ToShortTimeString()}";
await this.ShowChildWindowAsync(diagwindow, RootGrid);
Settings.Default.Save();
}
tried setting border thickness to 0, but doesnt seem to affect it
this is a new Window, that has only been changed to MetroWindow (nothing else added), uses Controls.xaml, Fonts,xaml and Light.Amber.xaml as resources
anyone an idea wat it might be?
great call @timunie
running the exe itself seems not result in that weird border like line
am running vs2022, so they might have some hickups still, although annoying, as long as it doesnt show up on my finished product, i can't complain :thumbsup:
knowing its not there when running the exe is good enough for now :thumbsup:
:+1: happy hacktober
in the test application (mahapps.demo) also has the same thing
also for context the top 2 are text boxes
Seems like the control template is broken
You can try to set
IsHittestVisible="false" and Focusable="false" and see if it helps you
