Ralph DiMola wrote:
> I did not know that. I thought all DNS was case insensitive not just
> the TLD. I never seen it to the contrary.
>
> The Unicode thing is scary though. It validates my surfing habits. I
> never use email links. If I get an email from say my bank I always
> type the URL into
PM
To: Ralph DiMola via use-livecode
Cc: Mark Wieder
Subject: Re: What the heck? Writing and reading ios files??
On 6/25/20 2:16 PM, Ralph DiMola via use-livecode wrote:
> FYI: So does Android.
>
> ...Imagine if we had case sensitive URLs or email addresses...
Um.
In that case, you'
Glad to see you got it working!
JB
> On Jun 25, 2020, at 3:25 PM, Prothero-ELS via use-livecode
> wrote:
>
> JB,
> Thanks for the comment. Yes, I went back to my previous use of “_” in the
> file name. All is working now. It was the difference between “l” and “L” in a
> file name. Sheesh!
>
On 6/25/20 2:16 PM, Ralph DiMola via use-livecode wrote:
FYI: So does Android.
...Imagine if we had case sensitive URLs or email addresses...
Um.
In that case, you'll probably be surprised to find out that URLs *are*
case-sensitive. It's only the TLD where it doesn't matter.
What *is* a pr
JB,
Thanks for the comment. Yes, I went back to my previous use of “_” in the file
name. All is working now. It was the difference between “l” and “L” in a file
name. Sheesh!
Bill
William Prothero
https://earthlearningsolutions.org
> On Jun 25, 2020, at 2:27 PM, JB via use-livecode
> wrote:
>
I don’t think the underscore character “_” should cause any problems
in the pathname but if you use a space in the name you need to be
sure and enclose the pathname in quotes or it will fail.
JB
> On Jun 25, 2020, at 1:53 PM, Terry Judd via use-livecode
> wrote:
>
> On 26/06/2020, 02:40, "use-
al Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of
prothero--- via use-livecode
Sent: Thursday, June 25, 2020 4:07 PM
To: JJS via use-livecode
Cc: proth...@earthlearningsolutions.org
Subject: Re: What the heck? Writing and reading ios files??
Folks:
Thanks fo
On 26/06/2020, 02:40, "use-livecode on behalf of William Prothero via
use-livecode" wrote:
Jacqueline:
Thanks for responding. I am really stuck on this.
I can write the file, and get a list of the files I write, but when I try
to read the file using the same code to create the fil
Folks:
Thanks for you input. What I found out is that the iPhone cares very much about
case in text, but running the app on my desktop didn’t care about case, so I
had a mystery solved only by going down every blind alley until I finally found
the offending code.
It also seems, but I haven’t te
Jacqueline:
Thanks for responding. I am really stuck on this.
I can write the file, and get a list of the files I write, but when I try to
read the file using the same code to create the filepaths, etc, the read
routine says the file doesn’t exist. It all works in the dev environment. I had
us
Hi Bill,
> Am 25.06.2020 um 02:35 schrieb prothero--- via use-livecode
> :
>
> Folks:
> I’m having a very weird problem writing then reading the same file on ios. I
> must be missing something very basic. I’ve checked the path to the file when
> it is written and it matches exactly to the path
Mobile is case-sensitive, desktop isn't. The "documents" folder should be
all lower case.
If that's not the problem then show us the lines of script that both create
the file path and retrieve it.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperacti
Another solution might be to copy and paste a file
or create a new file of any type and give it a name
like myPath or whatever. Put that file in the same
location of the directory you expect your other file
to show up in. You can use any method to get the
file path of your new file myPath and use
I didn’t test the code so I do not know what
is happening with the file. But and idea to
test for problems is only write code that will
put something like :Hello world!” into the file
and see if you can locate the file on your
drive. If you still have the problem at least
it can be fixed within t
Added info:
I’ve tried putting the files in “cache”, in the “Documents” folder directly,
and using
> put URL ("file:"&tFile)
to store the data. Didn’t change anything.
I also looked at the lesson on reading and writing livecode files. Nothing
helps.
I’m using Livecode Business 9.6.0 on a Mac r
Folks:
I’m having a very weird problem writing then reading the same file on ios. I
must be missing something very basic. I’ve checked the path to the file when it
is written and it matches exactly to the path when I try to read it. In the
read routine, I check for the file’s existence and it sa
16 matches
Mail list logo
