Folder cut/paste causes ghost in DB

Started by 6b6561, April 20, 2024, 05:02:39 PM

Previous topic - Next topic

6b6561

Hi,

I often move folders by doing a ctrl-x followed by a ctrl-v in the intended new parent folder. If you do a ctrl-x immediately followed by a ctrl-v in the same place then the folder will be gone but remain in the DB. The folder can be recovered by doing a ctrl-v in the intended destination. If you don't do the ctrl-v in the intended folder, then you will lose the folder that you wanted to move and you have an orphan directory in the media tree.

Kim

Mario

#1
I understand that you press Ctrl+X and Ctrl+V without moving first to another folder.
It would never have occurred to me to do this.
For IMatch, this should be a no-op, or maybe resulting in a beep or something to inform the user.
I shall have a look over the weekend.

Until then, please Ctrl+X, select the folder you want to paste to (not the same folder you have just cut into the clipboard) and then press Ctrl+V to avoid any problems.
-- Mario
IMatch Developer
Forum Administrator
http://www.photools.com  -  Contact & Support - Follow me on 𝕏 - Like photools.com on Facebook

Mario

This has been resolved for the next release.
-- Mario
IMatch Developer
Forum Administrator
http://www.photools.com  -  Contact & Support - Follow me on 𝕏 - Like photools.com on Facebook

6b6561

Quote from: Mario on April 20, 2024, 06:23:04 PMI understand that you press Ctrl+X and Ctrl+V without moving first to another folder.
It would never have occurred to me to do this.

Correct, this is nothing that would normally be performed, but I happened to do it by mistake. Took me some time to realize what happened.

no-op or beep seems like the right action. I must say that I'm really impressed how quickly you got this into the next release!

Mario

Quote from: 6b6561 on April 20, 2024, 08:00:58 PMno-op or beep seems like the right action. I must say that I'm really impressed how quickly you got this into the next release!
I fix bugs I can reproduce as quickly as possible.

Since this bug has been lurking since IMatch 5 (2016!), it seems not to affect many users and so I gave it a low priority - which does not require an immediate release of a new IMatch version.
The bug is fixed for the next regular update (I ship updates every 6 to 8 weeks).
-- Mario
IMatch Developer
Forum Administrator
http://www.photools.com  -  Contact & Support - Follow me on 𝕏 - Like photools.com on Facebook