Since I keep full backups, I decided to be a guinea pig
, but alas, no joy. I was not able to duplicate the original issue (accessing fullscreen via the browser and viewer, using the toolbar shortcut and F11) or helmut's possible scenario. Every time I pressed delete, I was given a prompt asking if I was sure I wanted to delete, then when I said yes the images went to the recycle bin. Also, I was not able to access ".." when cycling through the images in fullscreen. This is certainly a very serious issue, but as I see it, there are multiple things wrong with hic's situation:
- The arrow keys should have worked to cycle through the images. Since they weren't working, it makes me wonder if somehow he managed to move the focus into the left pane of the browser, and up to the parent directory, which was then deleted; however, I've been unable to figure out how to do that, and even if that were the case, the focus should have been brought right back to the fullscreen viewer, thereby making it impossible for the delete request to register for an item selected in the left pane.
- There should have been a dialog box asking for confirmation.
- The folders/files should have gone to the recycle bin (though if they were too big for it they wouldn't, and while Windows asks if you want to permanently delete in this case, XnView DOES NOT and just AUTOMATICALLY PERMANENTLY DELETES the files)
- Pressing the delete key on a folder in the left browser pane doesn't do anything (seems to be related to the Ctrl+C, etc bug)
- Pressing the delete key on the ".." shortcut in the right browser pane doesn't do anything
- All folders BELOW 'Pictures' were deleted, but not the 'Pictures' folder itself (unless hic misstated what happened). This would indicate that each and every folder was individually deleted, which seems very unlikely to have happened, especially considering I can't even get such a thing to happen by really trying.
This is all with the same version and same OS as hic. Please don't take this the wrong way, hic, but are you sure there's not something else you did that may have caused this? Or maybe even a failing hard drive is to blame? I'm happy to help and serve as a test platform for figuring this out, because if indeed XnView did somehow do this I consider that to be a fatal flaw, but as of now I'm stumped.