xsharp.eu

wriedmann wrote:when it comes to WPF, even X# is case sensitive.
You need to the declare the class in exactly the same upper/lower/camel case as you use in XAML,

FFF wrote: in your code i saw "ColorConverter" and "colorConverter"...

public partial class ColorConverter : IValueConverter

<TextBlock Background="{Binding Path=., Converter={StaticResource ColorConverter}}" Text="{Binding Name}"/>							

<local:ColorConverter x:Key="XcolorConverter" />
...
<TextBlock Background="{Binding Path=., Converter={StaticResource XcolorConverter}}" Text="{Binding Name}"/>							

ic2 wrote: Then it works, most of the times. Fine with me but still I don't understand why I should create that <local:ColorConverter x:Key="XcolorConverter" /> first. I'd it should work with Converter={StaticResource ColorConverter}} too.

NickFriend wrote:

ic2 wrote: Sorry Dick, I have no wish to offend, but this is what I was referring too in my earlier post.

Don't worry, because first I am not so easily offended and second you are often right with your remarks. Further I appreciate your style of countering my grumpy VS observations.

NickFriend wrote:

ic2 wrote: To use a converter in xaml you need to declare it as a resource. It doesn't matter whether it's in the local control resources, the window, or in app.xaml, as long as it's available to the xaml that wants to use it. Once it's declared as a resource, then you can use it, that's how it works.
Simply using Converter={StaticResource ColorConverter} will not work, because ColorConverter is not a StaticResource, it's a C# class.

Ah, that makes sense!

I thought I was actually declaring the resource because the line

Code: Select all

<TextBlock Background="{Binding Path=., Converter={StaticResource ColorConverter}}" Text="{Binding Name}"/>

is within a <TreeView.Resources> </TreeView.Resources> tag.

As I use XConverter now, this is defined within a <StackPanel.Resources> </StackPanel.Resources> tag as

Code: Select all

<local:ColorConverter x:Key="XcolorConverter" />

and yes, that looks more like a declaration. That explains it, thanks!

Despite my preference to pick a working solution from Stackoverflow or other coding sites I do like to actually understand what the code is doing

Dick

ic2 wrote:Don't worry, because first I am not so easily offended and second you are often right with your remarks. Further I appreciate your style of countering my grumpy VS observations./quote]

Someone has to kick back against the rubbish you write about VS!!

Anyway, glad the confusion around resources has been cleared up.

Nick

ic2 wrote: I solved it by temporary removing

Code: Select all

	<Window.DataContext>
		<local:ViewModel/>
	</Window.DataContext>

from the XAML using Textpad. VS now opened normal, I could paste that same code back and this time VS did not give the error or freeze.

NickFriend wrote:Someone has to kick back against the rubbish you write about VS!!

NickFriend wrote:[I have a very simple static class with just one boolean property "Runtime". I set it true in app.xaml.cs or somewhere like that at the start of the application.