I wanted to override the CustomFilterSelectionControl style, so I took the style from the DataPresenterGeneric.xaml However, the icons included in the Images folder don't seem to be valid PNG files.
Has anyone else seen or complained about the images? They don't work for me. Can anyone else verify that the images in "%Program Files%\Infragistics\NetAdvantage 2009.2\WPF\DefaultStyles\" don't work at all?
Is there a fix planned?
Hi Andrew,
Thanks for the fast response, I'll give that a try and see if it works. I think this is a great way of using the images without having to add them to my own resources, plus it shaves a couple of Kb off the build.
Sebastien D.
The images are embedded in the DataPresenter assembly. I'm guessing that you're looking for it directly in the Resources node of reflector but that shows the embedded resources. When an image or other object is marked as Resource in the project (as it must be for the xaml to reference it), the object is embedded into the assemblyname.g.resources embedded resource so you can look in that embedded resource to find the images.
The issue is that the default xaml is using relative references and externally those images are no longer relative. Rather than pull out the images from our assembly you could update the xaml to use absolute references using the pack notation. e.g.
<Image Source="pack://application:,,,/Infragistics3.Wpf.DataPresenter.v10.1;component/Images/Filter.png" Stretch="None" />
Can you tell me in which assembly file the images are supposed to be? I've looked everywhere but can't find them. These seem to be PNG files made with fireworks, shouldn't be too hard to fix them and make them available to clients, I'm sure a lot of customers are overriding your default styles.
I even tried fixing them myself with adobe fireworks but they're completely corrupted.
A quick response would be appreciated, thanks.
Hello,
Yes, we are aware of this issue. We are working on resolve this. In the meantime, you can apply new images or you can extract them from our assemblies using some code analysis tool - like .Net Reflector