I am using the XamTreeGrid filtering with FilterResultsDisplayMode="ShowWithAncestorsAndDescendants" and FilterAction="Hide"
When children or ancestors are of "filtered in" rows are displayed they are of a very low opacity (0.35 to be exact) which my users find very difficult to read. Snooping around I found this snippet within the themes:
<Trigger Property="IsOpacityReduced" Value="True"> <Setter TargetName="PART_RecordContentSite" Property="Opacity" Value="0.35" /> </Trigger>
Which jives with the documentation on RecordFilterAction.ReduceFilter docs: "Record’s DataRecord.IsFilteredOut, property will be updated as well as the RecordPresenter's RecordPresenter.IsOpacityReduced. The default templates trigger off this property to set the RecordContentSite Opacity."
I would like to set this opacity value to something much higher without re-templating the content presenter. I've tried several things without the desired results, including this style:
<Style TargetType="ContentPresenter"> <Style.Triggers> <DataTrigger Binding="{Binding RelativeSource={RelativeSource AncestorType=igDP:DataRecordPresenter}, Path=IsOpacityReduced}" Value="True"> <Setter Property="Opacity" Value="0.85"/> </DataTrigger> </Style.Triggers> </Style>
Any suggestions?
Alternative angle to the same problem: is there a way I can prevent the DataRecordPresenter from being flagged as IsOpacityReduced when showing as an ancestor or dependent. If so then I think I can style these rows based on IsFilteredOut and IsVisible flags.
Hello Matthew,
The filtered out rows' opacity in the XamTreeGrid are updated in accordance to the item that is filtered in and all filtered out items are expected to have a reduced opacity because the DataRecordPresenter's IsOpacityReduced readonly property is set to true. Therefore the behavior is considered an all or nothing approach changing the opacity is considered to be a new product idea.
You can suggest new product ideas for future versions (or vote for existing ones) at <http://ideas.infragistics.com>.
There are many benefits to submitting a product idea:
Direct communication with our product management team regarding your product idea.Notifications whenever new information regarding your idea becomes available.Ability to vote on your favorite product ideas to let us know which ones are the most important to you. You will have ten votes for this and can change which ideas you are voting for at any time.Allow you to shape the future of our products by requesting new controls and products altogether.You and other developers can discuss existing product ideas with members of our Product Management team.
Steps to create your idea:
1. Log into the Infragistics Product Idea site at http://ideas.infragistics.com (creating a new login if needed).
2. Navigate to the product / platform channel of your choice (e.g. WPF, Windows Forms, ASP.NET, HTML5 / Ignite UI, iOS / NucliOS, etc.)
3. Add your product idea and be sure to be specific and provide as much detail as possible.
- Explain the context in which a feature would be used, why it is needed, why it can't be accomplished today, and who would benefit from it. You can even add screenshots to build a stronger case. Remember that for your suggestion to be successful, you need other members of the community to vote for it. Be convincing!
- Include a link to this thread in your idea so product management will be able to look back at this case.
The Product Idea site puts you in the driver's seat and allows you to track the progress of your ideas at any time, see how many votes it got, read comments from other developers in the community, and see if someone from the product team has additional questions for you.
Thank you for contacting Infragistics.
Sincerely,
Michael Di FilippoAssociate Developer