Moritz Mœller

The logic is broken there. This image does _not_ contain deep data, just RGBA, `f16`/channel. OpenEXR is a complex format. My guess is that the way the `image` crate treats...

I had a look at some old EXRs I have laying around and common channel names for RGBA data range from `r,` `g`, `b` to stuff like `spaceship.red`, `spaceship.green`, `spaceship.blue`...

I found a description of the logic OpenEXR uses: > RGB channels are present if the either (a) the names of the channels in their entirety or (b) following the...

On this note: the docs do not say what *color space* the *linear RGB* (*color model*) used in [`egui::Rgba`](https://docs.rs/egui/latest/egui/struct.Rgba.html) is. "Linear RGB" is pretty meaninless w/o this information. Working on...

This should not be "basic `viuer` functionality". Basic `viuer` functionality should be to take an `image::DynamicImage` and display that. Nothing more. A user can add the `image` crate to their...

That said, you can add a bunch of features and forward them to the `image` crate in `viuer`'s `Cargo.toml`. While this saves users from pulling in `image` themselves, it doesn't...

So if you wanted to do this, it would look sth. like this: ```toml [package] name = "viuer" version = "0.8.1" authors = ["Atanas Yankov "] edition = "2021" description...

Another option is to put `print_from_file` behind a feature flag that enables `default-formats` and is _off_ by default (`default-formats` would also be _off_ by default). That would mean a crate...

Two things: is the `png` feature still needed on `image`? I think `image` should have `rayon` on by default.

Here is a [bunch of OpenEXRs](https://github.com/user-attachments/files/15855652/j0.3toD__OpenEXRs.zip). The names should explain what the data in there looks like. Images were generated by me, I hereby put them under a [CC0](https://creativecommons.org/publicdomain/zero/1.0/) license.