LiveCode Forums.

Posted: **Fri Jul 20, 2018 7:59 am**

This is interesting. When I do

on mouseUp
   set the caseSensitive to "true"
   
   set the "X" of btn 1 to "upper"
   set the "x" of btn 1 to "lower"
end mouseUp

and then open the Property Inspector of btn 1, the value of both properties seem to appear as "lower".

However, doing:

Code: Select all

set the caseSensitive to true;put the X of btn 1

--> "upper"

Code: Select all

set the caseSensitive to true;put the x of btn 1

--> "lower"

So it looks like the property inspector has a bug and cannot differentiate between x and X.

In fact after deleting the "x" from the property inspector, the displayed value of "X" was immediately updated to "upper"!

Best,
Panos
--

Posted: **Fri Jul 20, 2018 1:02 pm**

Panos.

If you do spend time on this, please recreate the scenario I described above when setting the two props in the inspector itself. Mine simply deletes the second case in the middle of my trying to create it.

Craig

Posted: **Fri Jul 20, 2018 1:11 pm**

Hello Craig,

I confirm what you describe. This might be a bug in the tree view widget (which is used in this section of the Property Inspector), rather than a bug in the inspector itself.

I will file a bug in the weekend.

Thanks for spotting this.

Best,
Panos
--

Posted: **Fri Jul 20, 2018 4:21 pm**

Thank you for chiming back in Panos

Only a little playing around with this today, in the 6 and 7.x series, I had no problem creating custom props a and A in the property inspector, however, even with caseSensitive set to true, apparently changing one changed the other.

I also realized that I should probably have started the testing in the newer 8/9 x series

but now I'm curious if this was always the case.

LiveCode Forums.

cAPITAL lETTER pROBLEM

Re: cAPITAL lETTER pROBLEM

Re: cAPITAL lETTER pROBLEM

Re: cAPITAL lETTER pROBLEM

Re: cAPITAL lETTER pROBLEM