It now seems to me that the issue is if you have
f.shellPath, and f.exists=false then you get the absolute path.
I tried referring to a non-existing file in the temporary items
folder. If this file is "F":
msgBox f.shellPath produces what you would expect from the absolute
path.
msgBox f.parent.shellPath+"\"+f.name gives you a dos path as you
would want.
If this rings as true, or as a valid bug, and anyone else wants to
report it, I would appreciate it. Long day, I'm spent... if it isn't
bugged by tomorrow, then I'll do it myself.
G'night.
C.
On Nov 8, 2006, at 11:56 AM, Tim Jones wrote:
On Nov 8, 2006, at 4:35 AM, Chris Halford wrote:
I'm on the same version, but I am seeing this on non English
installs. I'll try English when I get to the office today.
Careful here as I still suspect that something isn't right in RB
and I don't expect that language version makes any difference.
There is an outstanding shellpath issue that still seems to visit
itself upon us in seemingly random circumstances.
http://www.realsoftware.com/feedback/viewreport.php?reportid=kmzqjjsc
We've seen this on Mac and Windows even though the report focuses
on Mac. Sometimes we get back the Shellpath ( /Volumes/My
Volume ), sometimes we get the Shellpath duplicated ( /Volumes/My
Volume/My Volume ), and sometimes we get back the AbsolutePath ( My
Volume: ). All this from the simple:
fi.ShellPath
Call (fi is the FolderItem).
Tim
--
Tim Jones
[EMAIL PROTECTED]
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
