XnView Software

Hello

I have to report a very annoying repeating bug.
If you want to see it in action, I will describe how to evoke it:

1) Have a .jpg in a folder like example.jpg in [some folder]
2) double-click it to view it in xnview
3) close xnview
4) go to windows explorer (I use xplorer²)
5) try to delete the whole folder named [some folder]
6) error message:
[img=http://img135.imageshack.us/img135/9705 ... ge4.th.jpg]

Translation says: File cannot be deleted. The file or folder is in use by another person or program.

Hamlet

Hello !

• I can't confirm following your steps, the folder and its contain are deleted.
- I use Total Commander (Del+Shift >> no Recycle Bin).

• IMHO, XnView is not closed really when you attempt to delete the folder, but it continues tu run in the background
for some unknown reason, IIRC that occured for a user too a while ago (please, use the Search…).

Kind regards,
Claude
Clo

Really??? It's strange, you can reproduce it always?

Yep. Sometimes it even "works" with single files.
But the problem with the folders happens quite often to me...
I downloaded something, have a look at it, close xnview, decide to delete it - wham!

Very annoying... once I open another picture in another folder, I can delete the first folder at once, but never right after viewing a picture in it.

I can't reproduce, do you have the same problem with windows explorer not xplorer²?

I use xplorer2 pro v1.7.1.4 and I can't confirm this bug report.

Update:
I found out this problem also shows up with mp3 files. Same procedure:

- play a mp3
- close the program
- try to delete the folder, which contains the played mp3 file
--> error, file still in use

Funny thing though: If I try to delete a single file (be it a picture or a mp3 after viewing/playing, there is no error at all...

For the sheer fun of it, I created a folder with a .doc file in it and repeated the procedure. There, no problems deleting the whole folder!

Damn you, Windows!


Although it might not be a xnview-exclusive problem, I really would like to know how to stop this ill-behaviour.
Thanks for your attention.

Hamlet

Hello !

• No surprise if I tell you that the test with *.mp3 here is successful, all is deleted as expected…

• Just some thoughts :

1. When you have closed the dis¦played file and XnView, please check in the Task Manager (Ctrl+Alt+Del)
whether there is a running XnView process still…
- I there is not any, check too if an eventual other graphic thingy is running
(I think to a M$ one started wrongly too for the related extensions…).

2. From a decent File Manager, check which attributes the folder you want to delete has…
If you have Win Explorer only, right-click on it and choose “Properties” to see the attributes…

… and come back to tell us what you found out !

KR
Claude
Clo

Found it!

It was related to xplorer²...



Guess what the text says? "Do NOT lock the shown folder" - of course I had this one ticked... but once I un-ticked it, *magic* every folder deletes just fine...

I found out in the xplorer²-forums.
I really like that file browser... but those admins are real morons there... a user had the same problem like I had... found out the hard way, told them.. and they fail to see his point why this option needs some quick RENAMING...

Instead, they go like: "the simple workaround is to start another document, any document, from another folder, and the originally locked folder will be unlocked"

Yes... of course... if I can't delete what I say shall be deleted I go to another folder each time and open another mp3/jpg just so that stupid folder gets unlocked... that's what I call outrageous stupidity

...all it would take them is a simple change in one sentence of their program, so everyone can understand it...

Hamlet

Hello !

• Glad to hear that you found out the culprit !

• If I understand correcltly, the caption tells :
“Don't lock¦freeze the (current) displayed folder”
while it does the opposite ?

OMG ! Such a hitch is unthinkable in TC, moreover :
1. There is not such an option (causing troubles, obviously),
2. Anybody could edit and correct the used language file (it's plain text !).

• Well, anyway, your misadventure shall be useful here when similar issues are reported

KR
Claude
Clo