Hi,

Apparently that's a widespread problem:

http://social.msdn.microsoft.com/Forums/en-US/wpf/thread/5289ee56-6d06-4f66-84f2...

As a work-around you might try setting the diagram's SnapToDevicePixels property as well, setting such a GridSize that the grid points are aligned to device pixels, and then aligning all nodes to the grid.

Stoyan

I saw I had not always SnapToDevicePixels added to all elements in my test Xaml, and when I added that, the elements rendered sharp.

Until I collapsed the Expander, then the collapsed element was blurry as hell.

What I wonder is: in all your demos of the WpfDiagram control, you don't have blurry text once, also not with the HTML-like elements. It's of course unacceptable for us to have blurry elements on the diagram, but as your demos never show blurryness, I wonder where the error might be, as it IS possible (your demos show that ).

I read the thread, and I agree, it's the main reason why we opted for yet another Winforms based main UI, however for diagramming, Wpf seems easier, at least, at first, however it more and more starts to become a true pain as well...

I've specified my (modified test) xaml below.

<UserControl x:Class="SD.LLBLGen.Pro.Gui.Controls.WPF.EntityGlyph"
    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
	xmlns:c="clr-namespace:SD.LLBLGen.Pro.ApplicationCore.EntityModel;assembly=SD.LLBLGen.Pro.ApplicationCore"
    Width="150" SnapsToDevicePixels="True" Focusable="True" Height="Auto">
	<UserControl.Resources>
		<DataTemplate x:Key="itemTemplate">
			<TextBlock Text="{Binding Path=Name}" FontSize="10" SnapsToDevicePixels="True"/>
		</DataTemplate>
	</UserControl.Resources>
	<Border BorderBrush="Black" BorderThickness="0.5" CornerRadius="10" Padding="5" SnapsToDevicePixels="True">
		<Border.BitmapEffect>
			<DropShadowBitmapEffect Softness="0.355"/>
		</Border.BitmapEffect>
		<Border.Background>
			<LinearGradientBrush EndPoint="0.5,1" StartPoint="0.5,0">
				<GradientStop Color="#FFFDEEEE" Offset="1"/>
				<GradientStop Color="#FFF90909" Offset="0"/>
			</LinearGradientBrush>
		</Border.Background>
		<StackPanel Height="Auto" Width="Auto" SnapsToDevicePixels="True">
			<Label VerticalAlignment="Top" Height="Auto" Width="Auto" Content="{Binding Path=Name}" x:Name="_nameLabel" FontWeight="Bold"
			   FontSize="16" FontFamily="Tahoma" HorizontalContentAlignment="Center" Foreground="#FFFDEEEE" SnapsToDevicePixels="True"/>
			<Expander x:Name="_fieldExpander" Height="Auto" Width="Auto" Header="Fields" IsExpanded="True" SnapsToDevicePixels="True">
				<ListBox x:Name="_fieldsListBox" ItemsSource="{Binding Path=Fields}" BorderThickness="0">
					<ListBox.ItemTemplate>
						<DataTemplate>
							<TextBlock Text="{Binding Path=Name}"/>
						</DataTemplate>
					</ListBox.ItemTemplate>
				</ListBox>
			</Expander>
		</StackPanel>
	</Border>
</UserControl>
 

(updated the xaml a bit, it contained a lot of left-over crap from tests).

Even with a fixed width, it becomes blurry when collapsing the expander. It seems the element is rendered 1-2 pixels left of where it was. As your diagram does the positioning, I'm not sure if this is due to some wrapping code in the diagram item wrrapper.

Stoyo wrote on Jan 5^th, 2009 at 10:29am:

Hmm....

I think that might result in a lot of work, as expanders, listboxes and the like also likely will not make things work properly. :/

I look for a library which actually makes us write less code but if I still have to write out all the low-level rendering code, it's not worth the trouble nor the money.

I found some pixelsnapper code on an msdn blog, one variant didn't work the other one was simply very slow and also not really solving the mess. I ran into a topic about guidelines which should be used with a drawingcontext, but as I just supply a xaml object I don't see how I need to use them.

Your library was one of my last hopes of getting this done. As it seems you also don't know the answer, I guess we have to drop your library from our (now very short) list of libraries to use in our next version of LLBLGen Pro.