applejacko
About
- Username
- applejacko
- Joined
- Visits
- 0
- Last Active
- -
- Roles
- member
- Badges
- 0
- Posts
- 7
Reactions
Comments
-
Yeah, the thing is: it IS writing a file -- just to the "wrong" (unwanted) directory -- so it's not a permissions thing. I'm hunting through any information I can get on ofstream. The "open" member function takes two arguments: a const char* (…
-
rrabu, Thanks for trying this. I just tried your application verbatim (with changes just to the path and file names) using CodeWarrior and I got the same result I got before: a file named "/Junk/junkfile.txt" in my current directory instead of "…
-
Gents, The code is this simple: \t\t\t\t\tconst char* outputFileName = "/Junk/somefile.abc"; \t\t\t\t\tofstream outFile(outputFileName); \t\t\t\t for (int i=0;i
-
Madmax, thanks. I'm locked into using Carbon because I'm writing C/C++, not Objective-C or Java. And I'm locked into using CodeWarrior and C/C++ because I'm developing plug-ins for a specific application, and the SDK I'm writing against was built …
-
Thanks, but unfortunately this creates a file called: /somedirectory/blah/blah/targetfile.txt in the current (app launch) directory instead of a file called: targetfile.txt in the /somedirectory/blah/blah/ directory. There's gotta …
-
Thanks Karl. The problem I am having is that if I used a fully qualified path/file name to write a file, for instance, I get a file created in the directory of the application named as the full path + file instead of a file in the directory of the …