Paths too long on Windows Mobile?

[GoogleCodeExporter]

WinCE doesn't support paths longer than MAX_PATH.

We need to find a solution whereby gears on WinCE never creates files with
paths longer than MAX_PATH.

Original issue reported on code.google.com by gears.pl...@gmail.com on 19 Dec 2007 at 6:09

[GoogleCodeExporter]

Original comment by gears.te...@gmail.com on 20 Jan 2008 at 7:41

• Changed state: Accepted

[GoogleCodeExporter]

Andrei, is this currently a problem on Windows Mobile?

Original comment by gears.te...@gmail.com on 7 Mar 2008 at 8:20

• Changed title: Paths too long on Windows Mobile?
• Added labels: Version-later
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Yes, it is. The solution that playmobil implemented (UNC paths) only works on 
Windows
desktop. The file system API on Windows Mobile 5 suffers from the following
limitation (according to MSDN): "There is a default string size limit for paths 
of
MAX_PATH characters. This limit is related to how this function parses paths." 
So the
limitation is in the functions that parse a path, not the file system itself. 

The end of the conversation I had with Jeremy on this topic (December 4th, 
2007) was
the following:

"Jeremy: At any rate, this gives us a clear idea of the capabilities now. I 
talked to
Chris and we will add support for long names via the UNC paths to the File 
object to
push out this release. We will then come back and visit WinMO after this 
releas."

So we should revisit this, maybe after the 0.3 release.

Original comment by andrei...@gmail.com on 9 Mar 2008 at 4:31

[GoogleCodeExporter]

Original comment by gears.te...@googlemail.com on 6 Aug 2008 at 1:27

• Added labels: WinCE