Skip to content

Conversation

@taooceros
Copy link
Member

@taooceros taooceros commented Nov 25, 2020

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

  1. Use customized Async Image load instead of the one provided by WPF.
  2. Create Lazy Async class for doing 1.

Closing #42

@jjw24 jjw24 added bug Something isn't working review in progress Indicates that a review is in progress for this PR labels Nov 25, 2020
@jjw24
Copy link
Member

jjw24 commented Nov 26, 2020

just going to put through a commit to fix this issue i encountered while testing:

image

@taooceros
Copy link
Member Author

just going to put through a commit to fix this issue i encountered while testing:

image

Thank you for the fix!

@jjw24
Copy link
Member

jjw24 commented Nov 26, 2020

great fix, thank you 👍

@jjw24 jjw24 removed the review in progress Indicates that a review is in progress for this PR label Nov 26, 2020
@jjw24 jjw24 merged commit 2608d96 into Flow-Launcher:dev Nov 26, 2020
@jjw24 jjw24 added the kind/ui related to UI, icons, themes, etc label Nov 26, 2020
.Take(Data.Count - MaxCached)
.Select(x => x.Key))
{
if (!(key.Equals(Constant.ErrorIcon) || key.Equals(Constant.DefaultIcon)))
Copy link
Member Author

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.

Copy link
Member

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.

Copy link
Member Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working kind/ui related to UI, icons, themes, etc

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants