-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
glow
backend does not support Image
#674
Comments
Yeah, it looks like there's no |
Related to #354 |
Probably not the right place to ask, but is anyone working on |
The current Instead of porting the existing code to the |
Image
support for glow
backendglow
backend does not support Image
iced-rs#674 This works, but duplicates code from `iced_wgpu` that should ideally be shared, and the cache never evicts. The next step here is to work on an API design to move some of the image loading and caching logic from the backend to `iced_graphics` (or elsewhere?).
iced-rs#674 This works, but duplicates code from `iced_wgpu` that should ideally be shared, and the cache never evicts. The next step here is to work on an API design to move some of the image loading and caching logic from the backend to `iced_graphics` (or elsewhere?).
iced-rs#674 This works, but duplicates code from `iced_wgpu` that should ideally be shared, and the cache never evicts. The next step here is to work on an API design to move some of the image loading and caching logic from the backend to `iced_graphics` (or elsewhere?).
iced-rs#674 This works, but duplicates code from `iced_wgpu` that should ideally be shared, and the cache never evicts. The next step here is to work on an API design to move some of the image loading and caching logic from the backend to `iced_graphics` (or elsewhere?).
iced-rs#674 Uses image/svg support in `iced_graphics`. The is not currently using an atlas, and uses one texture/draw per image. This should be good enough for now; supporting images with glow is better than not supporting them, and if something else performs better, that improvement can be made without any change to the public API.
iced-rs#674 Uses image/svg support in `iced_graphics`. The is not currently using an atlas, and uses one texture/draw per image. This should be good enough for now; supporting images with glow is better than not supporting them, and if something else performs better, that improvement can be made without any change to the public API.
iced-rs#674 Uses image/svg support in `iced_graphics`. The is not currently using an atlas, and uses one texture/draw per image. This should be good enough for now; supporting images with glow is better than not supporting them, and if something else performs better, that improvement can be made without any change to the public API.
iced-rs#674 Uses image/svg support in `iced_graphics`. The is not currently using an atlas, and uses one texture/draw per image. This should be good enough for now; supporting images with glow is better than not supporting them, and if something else performs better, that improvement can be made without any change to the public API.
iced-rs/iced#674 Uses image/svg support in `iced_graphics`. The is not currently using an atlas, and uses one texture/draw per image. This should be good enough for now; supporting images with glow is better than not supporting them, and if something else performs better, that improvement can be made without any change to the public API.
iced-rs/iced#674 Uses image/svg support in `iced_graphics`. The is not currently using an atlas, and uses one texture/draw per image. This should be good enough for now; supporting images with glow is better than not supporting them, and if something else performs better, that improvement can be made without any change to the public API.
Is it possible to run the
tour
example with the glow backend? when I add theglow
feature to the example'sCargo.toml
I get the following error:It seems like the
Image
widget is not supported on theglow
backend.The text was updated successfully, but these errors were encountered: