-
Notifications
You must be signed in to change notification settings - Fork 692
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
Proposal: Create IconSource from Bitmap stream #601
Comments
@dotMorten is this blocking you from being able to adopt NavigationView in Xamarin? That would help inform the priority of this feature request. |
@jevansaks It's blocking me from using icons for sure. I could switch to use image controls, but these icons are used in quite a lot of places, and would be the natural thing to use. |
Here's the limitation in Xamarin.Forms: Only Forms' FileImageSource is able to convert to an IconSouce. All the other image sources are stream based. |
Reassigning this request to @ryandemopoulos to help route to the best owner. |
Thanks @dotMorten . Our team is pretty heads-down with Build coming next week, but we'll take a look at this soon (probably later next week). |
@ryandemopoulos Sounds good. I'll also be there all next week, if you want to chat face-to-face |
Just wanted to ask about the status of this issue => any idea if an when this will be done? |
Proposal: Create IconSource from Bitmap stream
Summary
Currently we can only create IconSources from bitmaps on disk or Uri endpoing. There's no way to create IconSources from arbitrary streams (like embedded resources), or pulling from a URI that needs custom authentication.
Rationale
Porting Xamarin.Forms' Shell to UWP, I'm hit with this limitation where icons are packaged differently with the app, and there's no guarantee that an icon is available on disk.
This means that in many scenarios the icons are rendered blank because there's no URI to map the resource to.
Functional Requirements
Syncronous instantiation to allow converters to return the correct type.
Can be loading pixels on-demand and async if needed, with knowledge of the DPI required.
The text was updated successfully, but these errors were encountered: