Custom copy: Name collision

[Enternal]

Yep! That's perfect!

[pat55]

Admin,
Just move the OK up one line or end of the lower 'overwrite' in your image.
You can keep the Cancel where it is.

The logic (without alternative facts) is that one has three equal weight and independent choices to click. Right now it looks like 4 choices
and what happens when you click OK is a 'mind-bender' to me also.
pat

[pat55]

Do this for the next "23 found" collisions.
Are the number of collisions not readily available?

One may know that they are all to be overwritten etc. or do something different based on the number of collisions found.
pat

[admin]

The number is not known at this point. (It could be roughly calculated but that would take time.)

Concerning the layout, what do you think of this (I show the current layout first for comparison):

Current Layout

overwritenold.png (23.43 KiB) Viewed 2858 times

New layout

overwritenew.png (23.54 KiB) Viewed 2858 times

[eil]

spaces above and below 2 file records should be even. button layout is ok

yet concerning collisions, their available number and "cases to decide" as a whole - maybe it's time for "leave all cases to end of operation" feature to appear?

[pat55]

I would move the Overwrite down one line.
For this sample - it is unfortunate that you chose overwrite in two places - it need not be so I think.

[pat55]

It should be - move the OK down one line.

[admin]

It's essential that OK is next to the dropdown. That's the main thing a wanted to achieve.

[pat55]

"It's essential that OK is next to the dropdown. That's the main thing a wanted to achieve."

Precisely - the overwrite OK is ONLY for the one line. The rest are all fixed buttons.

You will hopefully do this for both Copy and Move.
p

[pat55]

"It's essential that OK is next to the dropdown. That's the main thing a wanted to achieve."

Precisely - the overwrite OK is ONLY for the one line. The rest are all fixed buttons.

You will hopefully do this for both Copy and Move.
p

[admin]

You will hopefully do this for both Copy and Move.

I did.

[zer0]

Given how strongly I feel about GUIs, I could not help but chime in:

a) There is a lot of empty space to the right of file metadata and it feels like a waste. Given that vertical monitor space tends to be more limited than horizontal length, tall GUIs that overlap quite a bit of the background screen are not a good idea
b) I would like to see the number of collisions enumerated and listed in that "Do this also for the next collisions". If there is say 5 of them, I would not mind manually deciding what to do for each one, but if there is a 1,000 then it's a different story. Therefore, showing that information does have material effect on how a user is likely to act.

[admin]

Unused space is not automatically evil. It's relaxing.

a) The space will be filled when names get long.
b) Would take too much time.

[pat55]

You could even place a line around the 'long line' and the OK. (just as you have the arrow above -it is good)

Why did you move the long line back and away from the OK????????

[zer0]

Unused space is not automatically evil. It's relaxing.

I beg to differ. Unused space of dialogs and progress windows wastes my screen space underneath, thus forcing me to arrange things in a way that allows their display and work on other tasks. Good dialog windows strive for a compact and efficient look: the less unused space there is the better.

a) The space will be filled when names get long.

If you deal with long file names, you are in luck. However, not everyone does and most of the space under those dialogues would still be unused.

b) Would take too much time.

You may think so, but that is what Explorer already shows so it is normal for feature parity to be expected.