On Feb 27, 2007, at 1:53 AM, Tom Benson wrote:

>>> If you're comfortable with UNIX, why not just do this???
>>>
>>> dim s as new shell
>>> s.execute "mv "+source.shellpath+" "+dest.shellpath
>>
>> Because it also has to work on Windows.
>>
>> And besides, it seems like it *ought* to work. And I'd like to
>> understand this. FolderItems are kind of important...
>
> The SHELL example I provided will work fine on Windows too.
>
> But, if you want to understand.

Many thanks for taking the time to write all that out.

I'm no beginner with REALbasic. I'm trying to understand a corner  
case here. It seems a reasonable thing, to want to move a file to a  
file (the latter a FolderItem representing a file, that doesn't  
exist). This would constitute moving a file and renaming it in one  
step. This is something someone might well want to do, if you're  
moving a file to somewhere that already has a file with the original  
name of the file.

Now, I could live with doing move to folder - rename or rename - move  
to folder.

But moving to a file *does* work sometimes. If there was some weird  
voodoo I needed to understand that would make it work all the time,  
this would be convenient, and I would better understand the important  
FolderItem class.

So I'm looking for someone -- almost certainly someone from REAL  
Software, but possibly someone who has investigated this in detail,  
or had a reply to a bug report or some such -- to specify exactly  
when and how one can do a move of a file to a file.

Put it another way: this is weird. It works sometimes. Does anyone  
know what's going on?
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>

Reply via email to