cAPITAL lETTER pROBLEM

[richmond62]

So; there I am, feeling all over-confident tarting up the latest swanky version of my Devawriter Pro
when I came across a mAJOR pROBLEM tHAT i hAD cOMPLETELY mISSED bEFORE.

That really devolves on LiveCode.

If I have two images-as-buttons called "a" and "A' respectively and from somewhere else I

send mouseUp to image "a"

and

send mouseUp to image "A"

the SEND in both of those code snippets will "hit" only 1 of the 2 images.

This is because LiveCode is, seemingly, incapable of differentiating between lower and upper case Latin characters.
-

-

Capital crime.livecode.zip

Here's the stack.

(3.35 KiB) Downloaded 150 times

[Klaus]

Congrats, mate!

[LiveCode_Panos]

Hi all,

You could probably use the image ID instead of the image name in the send command.

In general, LC does differentiate between lowercase and uppercase letters but only when it comes to comparisons ("contains", "is among", "replace", "filter" etc)

See "caseSensitive" property in the dictionary.

However, messages, object names, and LiveCode terms are never treated as case-sensitive, even if the caseSensitive is set to true.

Hope this helps.
Panos
--

[richmond62]

Hope this helps.

Like most things: in some ways it does, and in others it doesn't.

As a naive realist (fancy, philosophical way of saying I believe what I see),
I find it convenient to give names to objects that make some sort of sense (to me at least),
and as I spend most of my programming life surrounded by objects with names such as "a", "A",
"z" and "Z" that 'problem' is a bit of a pain in the bum: renaming things like this: "xa", "A",
"xz" and "Z" is both tedious and a bit counter-intuitive.

On the teaching front, especially as I teach kids who, on a day to day basis, use
a non-Latin alphabet, explaining to them that LiveCode
is unable to differentiate between images called "abc" and "ABC",
but CAN differentiate between images called "щюя" and "ЩЮЯ" is a bit of a headache.

Oh, and, Klaus:

[bogs]

Just curious as I don't use simple naming, my controls and variables I usually name like I did in Delphi, cmdName(button), txtName(fields), grpName(groups), etc. (it helps fix an issue Jacque made me aware of with variables winding up tExt, as well as nigh guaranteeing I never use a reserved word )

Couldn't you in this kind of situation just use a simple if or case statement in the handler such as (psuedo code)

Code: Select all

put word 2 of the name of the target into tmpUpLow
if tmpUpLow is "a" then
	send mouseUp to image "a"
else 
	send mouseUp to image "A"
  // Of course, if you have more than 2 possibilities, go with select/case accordingly... 
end if

The ID as panos suggests would be the most accurate way, but if you already had your code setup it seems like to me you should just be able to wrap it in a case/select or if/then relatively quickly.

[richmond62]

In theory, bogs, yes . . .

BUT, while in my example stack SEND favours the image called "a"
in my Devawriter Pro SEND favours the image called "A" . . .

so hard to predict which one should be the default.

I suspect (?) that when the system has a choice between "a" and "A" it will
choose the object with the lower ID first.

[bogs]

In the code I gave as an example, what the system likes or doesn't shouldn't matter. In the example, your taking the name of the target, from your example, image "a" or image "A", getting the 2nd word of the name (which will either be a or A), and determining where to send the message based on that, which should be the correct image.

Or it is possible I just don't understand the problem correctly, I did only get halfway through my first cup of coffee so far

[Klaus]

Oh, and, Klaus:
saddlesore-sized.jpg

Again, I don't get this surely funny meme!?

But don't forget our "kinky relationship": "I educate (and make fun of you sometimes)
you, and you annoy me." And we are both very good at that!
http://forums.livecode.com/viewtopic.ph ... 01#p167189

[dunbarx]

Bogs.

LC cannot do what you imply in your handler. You cannot even determine the case of, say, the first char of the name of a control, since the caseSensitive property does not hold in that arena.

You must find another reference to work with. Richmond needs to rename his images.

Craig

[richmond62]

Again, I don't get this surely funny meme!?

Just put it down to cultural differences.

I educate (and make fun of you sometimes)
you, and you annoy me.

That sounds a bit arrogant.

Has it occurred to you that you might annoy me as well?

[richmond62]

Richmond needs to rename his images.

Indeed, and I did, and a right "bother" that was.

Why do I think it would be "rather nice" if this 'bug' were fixed?

[Klaus]

Again, I don't get this surely funny meme!?

Just put it down to cultural differences.

OK, it has to do with riding a bycycle, right?

I educate (and make fun of you sometimes)
you, and you annoy me.

That sounds a bit arrogant.

Your words (except the ones inside of the brackets), check the link!

Has it occurred to you that you might annoy me as well?

You BET, and in my opinion this is just fair!

[jacque]

Why do I think it would be "rather nice" if this 'bug' were fixed?

It isn't a bug. Case insensitivity has been normal for xtalk since HyperCard. In fact, LC improved on it by adding a way to distinguish it more easily during comparisons.

[dunbarx]

So much thinking and struggling just does not come up because of the case insensitivity of LC.

Certainly, as Richmond discovered, it may have its downside in certain situations, but that pales in comparison, and is easily circumvented. Sensible, robust naming is LC 101.

I recall a thread years ago that asked for a global property to make, er, the case for this to be optional in all aspects of the engine. I wonder how much stuff would break if this was misused, and whether the engine could even handle such a thing at this late date.

Craig

[richmond62]

Sensible, robust naming is LC 101.

And here endeth the lesson.

But, he who always wants to have the last word points out:

On the teaching front, especially as I teach kids who, on a day to day basis, use
a non-Latin alphabet, explaining to them that LiveCode
is unable to differentiate between images called "abc" and "ABC",
but CAN differentiate between images called "щюя" and "ЩЮЯ" is a bit of a headache.