Vanilla 1.1.1 is a product of Lussumo. More Information: Documentation, Community Support.
1 to 8 of 8
Thanx for the report. We will take a closer look on this one. I think that this is just hard coded buffer limitation, that would be easy to change.
When would you want a file name that is more that 260 characters?
There are staff here that copy/paste entire paragraphs explaining images and when they right-click and “Save As” for that image on a webpage, they paste the paragraph text into the filename… It may allow it, but you’ll have an extremely hard time MOVING that file from one drive to another (USB drive to HDD). The filename is too long. :)
...P.S. – I don’t condone using long filenames, I think the longest filename I’ve ever used has been less than 30. I politely yell at them when they do it. :P
tstrokes: File name has 255 characters limit, but file path may be up to 32767. It will better to support it :)
gbr: I made some prototyping about this and I discovered that there is very poor support for long paths in windows (xp). I mean that 99% of windows apps can’t work with paths longer than 255 characters. Here is my example command line application and you will see it. It creates a very long path in the C:\\!long_test directory.
I was shocked, that windows explorer can’t work, IE, Firefox, SciTE, totalcmd, winrar, visual studio and in the reality, every application which uses standard open file dialog can’t do this.
I’m going to make our file related code more “buffer overflow aware”. We may handle long files in command line parameters supplied to the Intype, but sorry, it’s impossible to create completely new open dialog :)
1 to 8 of 8