Re: Upper/Lower case issue

te. > > > > > > In the old HC days, before there was a name AND a label, I might have > > understood that you might have a valid reason to use identical names. You > > are aware that these two properties exist, and still have your reasons. > Can > > you say briefly what

Re: Upper/Lower case issue

On 7/2/11 5:51 PM, Dick Kriesel wrote: On Jul 2, 2011, at 9:42 AM, J. Landman Gay wrote: The entire engine is case insensitive, not just object names. Hi, Jacque. I guess that's why union and intersect can produce wrong results for mixed-case strings. Is that right? I haven't tried it, bu

Re: Upper/Lower case issue

Hi Chip, Thanks for chiming in and yes I know there is a label as well as a name. Further back in the thread, there's a explanation of what I'm trying to do. The whole problem arises because the casesensitive setting doesn't apply to object names so LC can't distinguish between two objects with t

Re: Upper/Lower case issue

Pete, I'm coming a bit late to this but... You do understand that a button's name is different from it's label. You can have a button named "fred1" with it's label set to: fred And another buttoned named "fred2" with it's label set to: FRED So the end user sees the difference as only upper

Re: Upper/Lower case issue

On Jul 2, 2011, at 9:42 AM, J. Landman Gay wrote: > The entire engine is case insensitive, not just object names. Hi, Jacque. I guess that's why union and intersect can produce wrong results for mixed-case strings. Is that right? -- Dick ___ use-

Re: Upper/Lower case issue

Thanks for all the good suggestions, they all have merit but I don't feel any of them are any better or worse than what I'm already doing. I understand and agree with the need to avoid duplicate object names but, once again, these are not duplicate names in any generally accepted sense of the word

Re: Upper/Lower case issue

On 7/2/11 11:43 AM, Pete wrote: Here's the code I used to get round the problem. You're doing way too much work. Name your buttons: %M 1 %m 2 %d 1 %D 2 Store the full button name in your prefs so that you'll have the correct name of the button to hilite when you need to set them. You won't

Re: Upper/Lower case issue

Pete- Instead of storing the button name in the preferences file, why not just save the button number? private command setButtonHilite pgroup, pbuttonNumber set the hilitedButton of group pgroup to pbuttonNumber end setButtonHilite -- -Mark Wieder mwie...@ahsoftware.net _

Re: Upper/Lower case issue

Pete, That's why we have custom properties. -- Best regards, Mark Schonewille Economy-x-Talk Consulting and Software Engineering Homepage: http://economy-x-talk.com Twitter: http://twitter.com/xtalkprogrammer KvK: 50277553 New: Download the Installer Maker Plugin 1.6 for LiveCode here http://q

Re: Upper/Lower case issue

what they are? > > I know you said they were too complicated, but just a one or two liner? > > > Craig Newman > > > > > -Original Message- > From: Mark Wieder > To: How to use LiveCode > Sent: Fri, Jul 1, 2011 8:56 pm > Subject: Re: Upper/Lower ca

Re: Upper/Lower case issue

On 7/2/11 12:27 AM, Pete wrote: But they're not the same name - one is upper case and one is lower case. LC made a decision to treat them the same since casesensitive doesn't apply to object names, but they are different by any other definition. The entire engine is case insensitive, not just

Re: Upper/Lower case issue

complicated, but just a one or two liner? Craig Newman -Original Message- From: Mark Wieder To: How to use LiveCode Sent: Fri, Jul 1, 2011 8:56 pm Subject: Re: Upper/Lower case issue Pete- Friday, July 1, 2011, 4:41:16 PM, you wrote: > That's OK Mark, I agree with what

Re: Upper/Lower case issue

But they're not the same name - one is upper case and one is lower case. LC made a decision to treat them the same since casesensitive doesn't apply to object names, but they are different by any other definition. In summary, the names of the buttons are strings that define elements of date forma

Re: Upper/Lower case issue

Pete- Friday, July 1, 2011, 4:41:16 PM, you wrote: > That's OK Mark, I agree with what you said 99.9% of the time, it's just > that there is a valid reason for what I'm doing in this particular instance. It seems like you found a way out of your predicament, but I'm still with Mark on this.

Re: Upper/Lower case issue

That's OK Mark, I agree with what you said 99.9% of the time, it's just that there is a valid reason for what I'm doing in this particular instance. Pete Molly's Revenge On Fri, Jul 1, 2011 at 4:27 PM, Mark Schonewille < m.schonewi...@economy-x-talk.com> wrote

Re: Upper/Lower case issue

Good call Devin, I found a way to do it using hilitedButton, coupled with the fact that comparing variables obeys the casesensitive setting. I have a repeat loop that cycles through all the buttons in the group, puts their short name into a variable, compares the short name variable with the name

Re: Upper/Lower case issue

Pete, I tried to make something clear something important, but you're free to disagree of course. -- Best regards, Mark Schonewille Economy-x-Talk Consulting and Software Engineering Homepage: http://economy-x-talk.com Twitter: http://twitter.com/xtalkprogrammer KvK: 50277553 New: Download th

Re: Upper/Lower case issue

Sorry Mark, I don't agree with you. Too complicated to explain by email but I can assure there is a good reason. Pete Molly's Revenge On Fri, Jul 1, 2011 at 4:06 PM, Mark Schonewille < m.schonewi...@economy-x-talk.com> wrote: > Pete, > > Use different names and

Re: Upper/Lower case issue

Pete, Use different names and equal labels. There is NEVER a valid reason to give objects the same name. -- Best regards, Mark Schonewille Economy-x-Talk Consulting and Software Engineering Homepage: http://economy-x-talk.com Twitter: http://twitter.com/xtalkprogrammer KvK: 50277553 New: Down

Re: Upper/Lower case issue

Pete, Does it work to set the hilitedButton instead of the hilitedButtonName? The former uses the number of the button, I believe. Devin On Jul 1, 2011, at 5:00 PM, Pete wrote: > I have two radio buttons whose names are identical except one is in > lowercase and the other is in uppercase. The

Upper/Lower case issue

I have two radio buttons whose names are identical except one is in lowercase and the other is in uppercase. They are in a group which should prevent more than one of them being set. The following statement ends up setting the hilite of both buttons: set the hilitedbuttonname of *group* "xyz" to