Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[dragyn]

When you move files and the file already exists and you select no to overwrite, MC still moves the file in the database. This is very very bad.

What happens is you have 2 entries in the database for the same file with different properties.

Please fix this. Maybe add a rename button or something when doing this or check to see if the file actually moved when done.

[Matt]

Thanks Dragyn.

It'll be fixed next build.

[dragyn]

Thanks for fixing it. Now my worries are over.  

[Matt]

BTW, the "replace all", "auto-rename all", etc. things would be great, but it'll have to wait for the next version.

[dragyn]

I tried moving some files with 277 and it asked to overwrite, said no, and it still moved the file in the database.

Moved from c:\ to \\<computer>\<drive>\<path>. Maybe it's something to do with the network drive?

[dragyn]

tried 280 and here's what it's doing:

moved some files. it asked to rename, said no. It didn't move the file but it moved the entry in the database.

One of my files was read-only and it didn't move the file (of course) but it also didn't move the entry in the database (good thing).

[dragyn]

...and we're movin' on up. la la la

[shAf]

Please post an acknowledement when this is fixed.  I was importing files last night, which were located in my "test" folder.  Once tested, tagged and evaluated, I intended to have them write over an existing subset.  I'm not sure of the sequence of events, but I ended up with a file disappearing ... not even to be found in the trash (... which was however replacable, but I could have otherwise been cursing all the way to bed ...<g>...)