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
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 a browser or a verified bookmark
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-
FYI: So does Android.
I always get pushback when I say "case sensitivity in file names is a
disaster waiting to happen". If doesn't waste a few days now it will later. The
push back is either purest or that it saves cpu cycles. If your running
Amazon's website then OK have a party with case se
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
Having another go at creating an iOS Share extension in Livecode.
Ben I had a go with the code snippets you supplied, but I’m not getting my app
appearing in the list of apps available to share. I had a bit of a goose around
and tried a bunch of options for the info.plist file without result - w
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
12 matches
Mail list logo
