Philipp Sumi

I noticed that this is triggered by the clamping decay function in `AnimationUtil`, and I eventually found the root of the issue to be the `decay` config here: const config...

Also, adding a new feed in VS2017 crashes VS with the explorer installed. Uninstalling the app from Windows Store fixed the issue.

@Lakritzator The snippet there looks dangerous. Despite the wrapping, you return a new Bitmap that will operate on a disposed object (the wrapped Bitmap). If that works, it still looks...

> Btw: > This actually also touches the following PR, it seems someone invested a lot of time 😁 > https://bitbucket.org/hardcodet/notifyicon-wpf/pull-requests/11/added-different-ways-to-set-the-icon/diff _cough_ :) Yes, let's revisit this one.

> In this example every time this is called, a stream is opened for something which is already there. When using this from animations, I could imagine caching it somehow....

CodeProject updated, waiting with others until there's anything new to show for (e.g. .NET Core support)

I'm fine altering the license if the CPOL impairs adoption. MIT would work for me 👍

I haven't tried it out yet on iOS, but is it possible that iOS expects base64 and Android a Hex string? The iOS sources seems to point towards base64, while...

@hairyhum this looks _slightly_ abandoned :). is the code here still up-to-date, or obsolete/incompatible by now?

It appears the current release doesn't contain the latest and greatest of FA. See here: https://github.com/jsmarcus/Iconize/issues/5 @jsmarcus - any update on this?