Harry Jeffery
Harry Jeffery
I'm taking another look at this. Right now imv is only equipped to deal with a single image at a time, I think what's needed is an image loader that...
Should be an easy enough change to the `imv_canvas_printf` function. I don't have the same coding time to devote to imv that I used to, but I'm happy to accept...
If you pipe the files to disk and run imv using that file as input does the same problem occur? i.e. `find . -type f | sort -V > images;...
Years ago when I first wrote imv it used multiple power-of-two sized textures to display the image. I don't remember the reasons for switching to a single-power-of-two texture, but I...
It's not a wontfix, the rendering just needs to be refactored to use multiple smaller textures when the image is too big for a single. I'm happy to review PRs,...
Closing as there's an easy workaround. If you feel strongly about this, you're welcome to lobby for it. There's a few things that'd need to be thought about: How should...
Reopening as something I'd accept PRs for. I currently don't have the time to implement this myself though.
Sounds reasonable enough. I'll try to get around to this in the near-future but I've been putting little time towards imv this year
Using inotify inside of `#ifdef __linux__` sounds reasonable enough to me. I'd rather opt-in to platform specific features where supported than use signals as a hack, so long as the...
All the major work for v4 is done, so I'd like to start doing the final clean up to prepare it for release. Therefore I'm afraid I'm pushing this improvement...