[iyonix-support] Re: Filer confusion when saving

In message <Marcel-1.53-0829084021-0b0pErr@xxxxxxxxxxxxxxxxxxxxxx>
          Chris Evans <chris@xxxxxxxxxxxxxxx> wrote:

> On Sat 26 Aug, John Harrison wrote:
>> 
>> I have an odd effect that has occasionally happened before, but I can't
>> explain.
>> 
>> Open new document in EasiWriter.
>> 
>> Try to save with filename Name in directory Parent.Child.   Get the
>> message: "Could not save file because Parent.Sibling cannot be created.  A
>> directory of that name already exists."
> 
> Which window are you dragging the file into?
> 
> If you are just clicking on o.k. it will be trying to save it as
> CSD.Parent.Child.DrawFile
> 
> If the full directory tree isn't there it won't create it!

That cannot be the problem here because the error would be completely 
different if the required directory tree was not there. Note the fact 
that the error is allgedly that "Parent.Sibling" cannot be created, it 
does not say anything about Parent.Child or Parent.Child.Name. The 
name "Sibling" seems to have come out of thin air (and it was the same 
for EasiWriter and Draw, so it was not the saving application making 
up that name).

>> Drag file to completely different directory - no problem.
>> 
>> Edit file and resave - also no problem.
>> 
>> In fact a file of the required name was created in Parent.Child , but
>> trying to open it gives:  "File produced by later version of EasiWriter
>> cannot be read"
> 
> Easiwriter seems to be managing to workout part of what you want to achieve
> but not properly:-)

Not quite. This just means that an empty file was created but 
EasiWriter could not write to it due to the abovementioned error 
returned by the OS. Note that EasiWriter, just as other RISC OS 
applications, does not attempt to create intermediate directories 
automatically, so if the directory Parent.Child is there, it has been 
there already. Actually, from what John wrote initially, I think he 
saves by dragging to the directory viewer for Parent.Child.

The original error report was not very clear and I suspect that 
"Parent.Child", and "Parent.Sibling" are not the real names involved. 
John, could you clarify please where exactly you save to (full path 
displayed in the title bar of the Filer window) and what the full 
error message is?

If it is really the case that saving a file to directory Parent.Child 
causes an error message about not being able to create file 
Parent.Sibling, then some utility in the background has messed with 
the file name.

Martin
-- 
---------------------------------------------------------------------
Martin Wuerthner           MW Software          lists@xxxxxxxxxxxxxxx
---------------------------------------------------------------------
---
To alter your preferences or leave the group, 
visit http://www.freelists.org/list/iyonix-support
Other info via http://www.freelists.org/webpage/iyonix-support

Other related posts: