I'd suggest that is Word's behaviour that it creates a temporary file, writes the buffer contents to the new file and then moves the new file over the old file. This behaviour is done so that if writing fails for what ever reason you don't end up with no file on your file system (e.g. run out of space or similar; delete then write new file) or a corrupt file (e.g. edit file contents in place). This is usually happens so fast that as an end user you don't notice it particularly if you're not looking at the file system at the time in a file browser which has event update notifications that are quick enough to refresh the display.
Cheers, Sam Moffatt http://pasamio.id.au On Wed, Nov 9, 2011 at 8:38 PM, hammer7 <[email protected]> wrote: > Hi, > > I was testing the Objc LoopbackFS with OSXFuse 2.3.4. > And i found that when i try to save doc/docx file on the loopback > drive, the file name changed from name.doc to something like Word > Work File D_642980228.tmp. > I guess exchangeDataOfItemAtPath is causing the problem. If i don't > implement that function, it's Ok. > I was testing it on Lion 10.7.1 with XCode 4.2. > > Thank Macfuse and OSXFuse authors for such a valuable open source > project. > > -- > 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. > > -- 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.
