[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problem in FSPathMakeRef() ??

Subject: Re: Problem in FSPathMakeRef() ??
From: Chris Espinosa <email@hidden>
Date: Tue, 13 Sep 2005 13:12:58 -0700
Delivered-to: email@hidden
Delivered-to: email@hidden


On Sep 13, 2005, at 9:07 AM, darpan kamboj wrote:

OSStatus err;
OSErr error;
FSRef ref;
const char *cCompletePath;
err=FSPathMakeRef((const UInt8*)cCompletePath, &ref, NULL);
error=FSCreateDirectoryUnicode (&ref, pFileName.length(), (const UniChar*) pFileName.unicode(), kFSCatInfoNone, NULL, NULL, NULL, NULL);


Where do you get pFileName ?

What's the value returned in error? You also don't seem to check whether the FSMakePathRef succeeds. Does it?

You declare cCompletePath as a char *, but later cast it to a UInt8*. These are different. How do you get the characters into it? Where do the characters come from? Are they canonically decomposed UTF-8 characters?

If you've been reposting because nobody has answered your question, it may be because you have not provided enough information for people to gather any idea what's going wrong.

Chris
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden

This email sent to email@hidden

Follow-Ups:
- Re: Problem in FSPathMakeRef() ??
  - From: Rosyna <email@hidden>

References:
	>Problem in FSPathMakeRef() ?? (From: "darpan kamboj" <email@hidden>)

Prev by Date: Re: Too long file paths. Should I really care?
Next by Date: Re: Too long file paths. Should I really care?
Previous by thread: Re: Problem in FSPathMakeRef() ??
Next by thread: Re: Problem in FSPathMakeRef() ??
Index(es):
- Date
- Thread

Home