-
-
Notifications
You must be signed in to change notification settings - Fork 455
Fix image flickering #221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix image flickering #221
Conversation
Co-authored-by: Bao-Qian <[email protected]>
… of updating lazy class async
|
great fix, thank you 👍 |
| .Take(Data.Count - MaxCached) | ||
| .Select(x => x.Key)) | ||
| { | ||
| if (!(key.Equals(Constant.ErrorIcon) || key.Equals(Constant.DefaultIcon))) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Question: Should we keep this two here in resizing check? I think the ErrorIcon should be replaced with MissingIcon, though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree, I think we should replace error with missing. Ideally missing img usage should be low, but I still see it often when using Explorer plugin, so since missing and default imgs are commonly used, we should continue to exclude them from removal. I will make a separate pr just to keep it clean.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think since they are commonly used, their usage won't be low so that they won't be removed. If they are low, then just removing them won't cause some issue.
Btw, I think we should use Except in Linq to except the key that we don't want to remove, which seems more clear.

This PR cherry pick some of the commit in #195 related to the flickering fix.
Closing #42