Copying - Source vs Destination folder highlighting

[Mesh]

The way XY currently works, when you copy items from one folder to another, XY shows and leaves the focus on the destination folder. The problem with this is that it makes it look like the contents of the file list pane belong to the highlighted folder - but that's not accurate.

I would suggest that the primary highlight be kept on the source folder, and if anything, the destination folder can have secondary highlighting (i.e. the thin outline box around the folder name, but without the selection highlighting).


This would make it clear what was the source, what was the destination, and what folder the contents of the file list pane belong to.

[admin]

AFAIk it's Windows standard as it is now.

[Mesh]

AFAIk it's Windows standard as it is now.

If you try copying files in Windows Explorer, you'll see that it's the source folder that retains the focus, not the destination. The same holds true in other file managers that I've tried - XY is the only place I've seen this reversed.

[admin]

AFAIk it's Windows standard as it is now.

If you try copying files in Windows Explorer, you'll see that it's the source folder that retains the focus, not the destination. The same holds true in other file managers that I've tried - XY is the only place I've seen this reversed.

I was thinking of drag'n'drop (and it behaves everywhere as I said)... and you?

[jacky]

I was thinking of drag'n'drop (and it behaves everywhere as I said)... and you?

I think he means D&D indeed, but there seems to be a couple differences between XY and Explorer :

- during the d&d, the highlight for selected goes to the potential destination (hovered) for both, but Explorer puts the focus indicator (dotted box) around the source/current location (even if Tree didn't had focus)

- what I think he means : once you dropped/released the button, XY let the destination highlighted on Tree, whereas Explorer gives it back to the source/current location. So in XY, if could appear as if the destination was the current location, though it's not obviously.

Note that AFAIC I don't mind the way it currently works, as it's a clear indication of whether or not the fileop is completed or not. And as long as the Tree never scrolls on its own, I'm fine.

But, with "File operation progress dialog modeless" enabled, it can feel pretty confusing/like a bug, since one can use XY while the fileop goes on, does the selected, or "highlighted", item on Tree isn't the current location, as it should be, but the destination.

[admin]

I was thinking of drag'n'drop (and it behaves everywhere as I said)... and you?

I think he means D&D indeed, but there seems to be a couple differences between XY and Explorer :

- during the d&d, the highlight for selected goes to the potential destination (hovered) for both, but Explorer puts the focus indicator (dotted box) around the source/current location (even if Tree didn't had focus)

- what I think he means : once you dropped/released the button, XY let the destination highlighted on Tree, whereas Explorer gives it back to the source/current location. So in XY, if could appear as if the destination was the current location, though it's not obviously.

Note that AFAIC I don't mind the way it currently works, as it's a clear indication of whether or not the fileop is completed or not. And as long as the Tree never scrolls on its own, I'm fine.

But, with "File operation progress dialog modeless" enabled, it can feel pretty confusing/like a bug, since one can use XY while the fileop goes on, does the selected, or "highlighted", item on Tree isn't the current location, as it should be, but the destination.

Ah, okay, thanks.

This behavior is so difficult to change that I simply don't want to do it now. I keep it in the back of my mind though.

[Mesh]

But, with "File operation progress dialog modeless" enabled, it can feel pretty confusing/like a bug, since one can use XY while the fileop goes on, does the selected, or "highlighted", item on Tree isn't the current location, as it should be, but the destination.

Ah, okay, thanks.

This behavior is so difficult to change that I simply don't want to do it now. I keep it in the back of my mind though.

I wouldn't have thought this behavior to be complex, as it seems like a small thing, but thank you for considering it for the future.

And thanks, Jacky for explaining!

[admin]

I wouldn't have thought this behavior to be complex, as it seems like a small thing, but thank you for considering it for the future.

Well, the change would be done in a minute, but the testing... drag'n'drop debugging is a bitch.

[Mesh]

Well, the change would be done in a minute, but the testing... drag'n'drop debugging is a bitch.

Gotcha!