My bad! I was returning an empty dictionary for a file which did not exist, making the finder think it did exist. So createFile was never called. Sorry!! And thanks!
On Dec 29 2008, 10:46 pm, "ted bonkenburg" <[email protected]> wrote: > On Mon, Dec 29, 2008 at 9:14 AM, iDeveloper <[email protected]> wrote: > > > Thanks for the reply Ted > > > I have changed the implementation for createFileAtPath already. I > > checked both with dtrace and debug mount option. The method is not > > getting called. I think I might've made a small mistake but am not > > able to pin-point it! > > > I'll go through the code and see if I can find the problem. > > Have you tried "touch" from the command line? That should certainly > lead to a createFileAtPath call. > > touch /Volumes/MyFS/some_new_file > > Also make sure that you are not mounting read-only and that the > directory where you want to create the file has write permission :-) > > ted > > > > > On Dec 29, 10:03 pm, "ted bonkenburg" <[email protected]> wrote: > >> On Mon, Dec 29, 2008 at 7:37 AM, iDeveloper <[email protected]> > >> wrote: > > >> > Hi > > >> > I am trying to implement a writable file system. Initially when using > >> > MacFUSE 1.7, when I dragged a new file to the FS, createFileAtPath was > >> > getting called. After switching to 2.0, when I do the same operation, > >> > createFileAtPath is not called. Instead first I get a prompt saying > >> > the file already exists and then the operation fails. The file is > >> > created momentarily. But then later it is deleted (I guess thats > >> > because the finder rollsback the operation) > > >> The selector for createFileAtPath: changed between 1.7 and 2.0. > >> However, the code should still be calling the old-style selector if > >> the new one is not implemented. Can you try changing to the new one > >> and see if it gets called then? > > >> - (BOOL)createFileAtPath:(NSString *)path > >> attributes:(NSDictionary *)attributes > >> userData:(id *)userData > >> error:(NSError **)error; > > >> Also, how are you confirming that it is not called? Did you try using > >> "touch" from the command line to see if it works at a simpler level > >> (non-Finder)? Have you tried using dtrace to confirm that your > >> createFileAPath: is not being called? > > >> > Using the debug option shows that the attributesOfItemAtPath returns > >> > proper errors initially when it is called when the file does not exist > >> > yet). But even then createFileAtPath is not called and I get the > >> > prompt that the file exists. > > >> Make sure stuff works on the command line before trying the Finder. > >> Can you do the basic file operations on the command line? > > >> You might find some of the information in our recent talk useful. I > >> did a section on the Objective-C library. The video can be found here: > > >>http://www.youtube.com/watch?v=cY8lBOSO3ak > > >> ted > > >> > Can someone please tell me where I could be going wrong? > > >> > Thanks. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MacFUSE" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/macfuse?hl=en -~----------~----~----~----~------~----~------~--~---
