DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2733 Version: 1.3.0 I see.. subject line has the details about MAX_PATH which I missed. I was only looking at the STR's body. Wow, the OS's own setting for MAX_PATH is 260? Good grief. OK, seems this page covers the details: http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247%28v=vs.85%29.aspx#maxpath ..which seems to reduce to: 260 -- for 'local' drive letter paths (eg. c:\bla..) 32767 -- for 'extended' paths (eg. "\\?\D:\bla\bla..") I imagine UNC paths qualify for the latter as well (eg. "\\server\volname\bla..") Will probably have to make our own macro and set it to 32767 to get past this, but I'll check if it's possible to use dynamic arrays. FWIW, quoting the relevant info from the above link in case it goes stale: In the Windows API (with some exceptions discussed in the following paragraphs), the maximum length for a path is MAX_PATH, which is defined as 260 characters. A local path is structured in the following order: drive letter, colon, backslash, name components separated by backslashes, and a terminating null character. For example, the maximum path on drive D is "D:\some 256-character path string<NUL>" [..] The Windows API has many functions that also have Unicode versions to permit an extended-length path for a maximum total path length of 32,767 characters. This type of path is composed of components separated by backslashes, each up to the value returned in the lpMaximumComponentLength parameter of the GetVolumeInformation function (this value is commonly 255 characters). To specify an extended-length path, use the "\\?\" prefix. For example, "\\?\D:\very long path". Sounds like we'll have to hard code the 32767. Link: http://www.fltk.org/str.php?L2733 Version: 1.3.0 _______________________________________________ fltk-bugs mailing list fltk-bugs@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-bugs
