MaterialDesignInXAML / MaterialDesignInXAML/MaterialDesignInXamlToolkit

Feature Request: ListBox / ListView with option of triggers instead of visual states (such as gridview) for better performance

Open
#2,953 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug evaluation required
Dominant language
C#
Stars
16.3k
Forks
3.5k
Avg merge
1d 22h
Merged PRs (30d)
8

Description

### ~~Bug explanation~~ Feature Request

Hi and Thanks for your awesome library :)

Trying to implement my first WPF project (a media player) based on Material Design but I'm having a lot of performance issues.
The serious one is with ListBox / ListView when the mouse is over which I will try to investigate further by customizing the templates.
You can reproduce it easy with the DemoApp Lists and check your task manager (add GPU column).

I have also other performance issues mainly on full screen with a drawer (seems related to #1116).

Regards,
John

### Version

4.6.1 and latest beta

## Updates

1. Even when I use materialDesign:ListBoxItemAssist.ShowSelection="False" and it will not happen anymore mouse over but it will happen on mouse click
2. It looks like it is also affected by WindowStyle="None" ResizeMode="NoResize" AllowsTransparency="True"
3. OK it's the ripple and visual states but again I think it's not normal (still looking and possible will close this)
4. Closing this but ideally I should be able to use some basic mouse over and ripple with low resources

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the DemoApp Lists reproduction and inspect the ListBox/ListView behavior around mouse-over, selection, ripple effects, and visual states. Compare the performance impact of the current visual-state approach, including WindowStyle="None" with transparency; done would require a clearly scoped low-resource trigger-based option and a way to verify the improvement.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop, performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.