You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You probably need to re-enable some of the features disabled by default-features = false to regain the support for decoding your textures, just don't enable the threading/rayon features.
has this crate been used in the browser?
my project uses the image crate and is being ported to wasm32/emscrioten;
it crashes on startup reporting that threads arent available;
i can get it past that using “default-features = false” but then its not managung to decode textures (as far as i can tell)
Q1 could anyone verify if this should work
Q2 could the library default to no threading on the wasm targets
whats the thinking on this
The text was updated successfully, but these errors were encountered: