The community Taskforce initiative has now come to a close.
Thanks to everyone who made thoughtful and genuine contributions to the website.
All submissions will be kept publically available for the forseeable future for reference purposes.

This website is part of the community Taskforce initiative

Submission details

29 +30/-1 votes

Missing button - Destination path too long

Submitted by Beun on January 17, 2010 to Usability

When a file is being copied but the filename becomes too long, windows tells you this. However, windows does not give you the option to rename the files, it only gives the option to skip or cancel the copying of these files.

Add the option to rename these files.

Medium

Low

Not fixed

Discussion (12 comments)

.Chris wrote on January 17, 2010, 9:21pm

Here is what it should look like:

http://farm5.static.flickr.com/4064/4282826014_4ef9337263_o.jpg

Program I used:

http://www.codeproject.com/KB/vista/TDXMLLibrary.aspx

Works great in windows 7

Comment edited on January 17, 2010, 9:22pm

Comment edited on January 17, 2010, 9:22pm

Indrek wrote on January 18, 2010, 1:20am

+1

Nice mockup, Chris.

Calum.Cook wrote on January 18, 2010, 9:49am

Yeah, nice mockup :)

xombie wrote on January 18, 2010, 5:20pm

Nice mockup, .Chris, but don't the No and Cancel buttons do the same thing?

+1

Beun wrote on January 18, 2010, 5:33pm

@ xombie,
No and Cancel have different functions. Cancel cancels the entire copy/move process. No just cancels the copying/moving of those files that create a path name that is too long.

xombie wrote on January 18, 2010, 6:55pm

Ah, should be skip like the other dialogs, i guess.

patternjake wrote on January 19, 2010, 6:42pm

I agree with his mockup +1.

Going to check that program out btw.

.Chris wrote on January 19, 2010, 6:44pm

Yeah its great if you need to make a mock up. They also have the XML code, as well as other programs.

pmbAustin wrote on January 22, 2010, 6:00am

How about fixing the ridiculous 260 character windows file path limit?? :-)

patternjake wrote on January 27, 2010, 6:52pm

pmbAustin : That is a limitation in NTFS. Something like that cannot be changed over night. A whole update to the bits address spacing in NTFS would need to be done to cope with that, which would require a new OS essentially.

I think that W8 will have a new file system anyway to cope with issues like that.

ryan wrote on March 10, 2010, 1:07pm

I'll confess, I got pretty excited to see .Chris's UI shots. It made me think they were a real solution at first. sigh...

You might also be interested in...