Thanks for making XnView, but *please* fix this highly frustrating bug when saving images!

[forcedtopickone]

First of all: Thanks for making XnView. I have used it for so many years and found it impossible to replace. It does have some bizarre defaults (like every software I've ever used), but once set up, it's fantastic. So thanks for that.

However, there's something which has been driving me insane about it for many years, and seemingly has been made much worse recently. I have just installed a new PC with new Windows 10 and new XnView (less than a couple of weeks ago).

Basically, whenever I crop an image (which I do a million times a day) and then try to load the next image (so that the "Do you want to save?" box pops up), it asks one or both of these questions, over and over again, no matter how many times I check the checkboxes.

"Be careful, saving in this format will lose existing metadata!"
"[ ] Do not show this message again."

"Do you want to save changes to 'file name'?"
"[ ] Never ask again"

Some files seem to not get one of the questions, but all files always display at least one of them. XnView seems to simply not have implemented the checkboxes. They don't seem to be saved, or, if so, they aren't respected. I don't know what to make of this since it's been the case for so long, and I believe that the author must know about it.

If you do know about this bug, how come it hasn't been fixed? I truly hope that you haven't become completely apathetic like the Deluge/VLC/MPC-HC/FileZilla/WinMerge or just-about-any-freeware-and-or-FOSS-developer these days... because that makes me genuinely sad and worried for the future of the desktop computer, on top of just being frustrating for me personally.

Please note that I did try the new XnView multiple times, but it was... well... I don't want to insult you, but it did the classic mistake of trying to redo something from scratch (which is extremely tempting and I've done it myself many times), but while doing so losing what made the original product so great. It's too complex to go into details about why that happens here, but it does seem like you are still developing the "classic" XnView, so I don't see why this bug should not be fixed. Maybe the author never crops/saves images in his own application? That's just about the only reasonable explanation to me.

[XnTriq]

Please refer to my step-by-step instructions.

[forcedtopickone]

Thanks. That fixed it, apparently. Nice. I will save those instructions for the next time this (probably) happens in the future.

What confuses me is how that situation occurs in the first place, though. I don't recall doing anything "weird" at any point to cause it...

[forcedtopickone]

It should be noted that while your fix works, it works a bit *too* well in that it completely skips asking the user before it saves any changes. This was not quite what I was referring to (or was it?*), and makes me constantly paranoid that I will accidentally flip a JPEG or something and then browse to the next image and have XnView auto-save the accidental/unintended change and thus losing data (quality) forever for that image, perhaps not realizing it until much later.

* I can't exactly put into words what behaviour I want from XnView. I just know that the way it is now is a bit scary and the way it was before seemed broken (as it didn't seem to register the checkboxes). It definitely does feel like it's asking too many questions by default.