It's not supposed to exist, and it's not a permissions issue.
I'm sure that this error may be raised if you attempt to create a
FSSpec (and maybe even a DataRef too) from a string for some path
that does not yet exist - which is problematic if you're trying to
create a new file.
A hack to workaround this problem is to touch the filepath yourself
(so that it exists on disk) prior to referencing it with your
QuickTime API calls, which is similar to what Richard Ramsden
suggested you could do earlier in this thread.
Hey hey! That's worked. The file has to exist before it works if a
colon is in the POSIX path. How odd. Thanks!
*updates the bug report*
--
Seth Willits
_______________________________________________
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
