-
-
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
Merged
Merged
Fix image flickering #221
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
2c14c21
Lazy Load Image
bao-qian 1439ee7
Use a default image to list when the image hasn't been loaded in cache.
taooceros 99086e2
change SetImage to method instead of property to avoid unintended use
taooceros a7310d5
Use Customized LazyAsync class to load image instead of the weird way…
taooceros b3df2fd
change default image property name
taooceros dd8a31c
Add new to Value Property of the LazyAsync clas
taooceros efcb6a7
add status check when base.Value has faulted
jjw24 ac945f4
revert unneeded condition on Constant.MissingImgIcon
jjw24 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.