on 7/23/00 8:10 PM, [EMAIL PROTECTED] at
[EMAIL PROTECTED] wrote:
> I don't understand how the above can work: don't you need a "/" before the
> "proxyPrefs.txt"?
Yes you are right. . ."/proxyPrefs.txt" is needed.
>> on mouseUp
>> put the directory & "/data/proxyPrefs.txt" into tPath
>> put tPath into msg
>> put "204.148.111.2" & ":"& "8080" into url ("file:"&tPath)
>> end mouseUp
>>
>> this doesn't work. Why?
>
> Does the folder "data" exist? What does the result contain after you run
> the put into URL?
No, the folder "data" does not exist. the result is "can't open file."
I am trying to create the folder at the same time as I write the file. This
would indicate this is not possible, under the url suite of file management
in a single put statement. . .,
This does work:
Example ONE
on mouseUp
create directory "mcPrefs"
put the directory & "/mcPrefs/proxyPrefs.txt" into tPath
put "204.148.111.2" & ":"& "8080" into url ("file:"&tPath)
end mouseUp
This also works:
Example TWO
on mouseUp
create directory "mcPrefs"
put "204.148.111.2" & ":"& "8080" into url ("file:mcPrefs/proxyPrefs.txt")
end mouseUp
OK, I am getting a better handle on this.
the following DOES NOT work (no slash before the "mcPrefs/ in line two
on mouseUp
create directory "mcPrefs"
put the directory & "mcPrefs/proxyPrefs.txt" into tPath
put "204.148.111.2" & ":"& "8080" into url ("file:"&tPath)
end mouseUp
Question:
Why, in the Example Two above, is a slash not required after "file:" in
("file:mcPrefs/proxyPrefs.txt")
but it IS required to be passed in the two line scenario in Example One? Is
it because in example one we are creating a single string that has the
entire path all the way from the user's hard drive down. . .but that
put "204.148.111.2" & ":"& "8080" into url ("file:mcPrefs/proxyPrefs.txt")
Assumes the default directory and a slash will be transparently implied? If
I got that right then, ha, I think our "directory" training is finally over.
Thanks
Hinduism Today
Sivakatirswami
Editor's Assistant/Production Manager
www.HinduismToday.com
[EMAIL PROTECTED]
Archives: http://www.mail-archive.com/metacard%40lists.best.com/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
