The problem is when I make the FSSpec with the FullPath. When the FullPath is greater than 127 characters the "name" of the FSSpec file ends with garbage.
Do you know another function to make the FSSpec? I'm currently using FSMakeFSSpec or NativePathNameToFSSpec.
Thanks in advance.
---------- Forwarded message ---------- From: Germán Gonçalves <email@hidden
> Date: 12-ago-2005 12:50 Subject: large File Paths in Windows To: email@hidden
Hi, I need help, I made an OCX with Microsoft Visual C++ 6.0 using QT lib to use it within a .NET application. This works fine but when I have a File Path with a length grater than 127 it crashes in the "PToCstr((char*)theFullPath);" function with no error. Previously the CToPstr function works fine.
If the File Path is grater than 145 then "OpenMovieFile(&sfFile, &movieResFile, fsRdPerm);" returns a error value.
Can you help me with this?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
QuickTime-API mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quicktime-api/email@hidden
This email sent to email@hidden
