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 the same name but in different cases. But I'm sure you already know that. Pete Molly's Revenge <http://www.mollysrevenge.com>
On Sat, Jul 2, 2011 at 5:33 PM, Chipp Walters <ch...@altuit.com> wrote: > 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 and lower case, whereas > your program differentiates them correctly by their unique names. > > I wasn't sure this was clear to you. > > > > Chipp Walters > CEO Shafer Walters Group, Inc > > On Jul 2, 2011, at 2:26 PM, Pete <p...@mollysrevenge.com> wrote: > > > 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 no matter what LC thinks of them - their case makes them unique - so > I > > don't feel like I'm breaking any golden programming rules. > > > > > > Pete > > Molly's Revenge <http://www.mollysrevenge.com> > > > > > > > > > > On Sat, Jul 2, 2011 at 9:42 AM, J. Landman Gay <jac...@hyperactivesw.com > >wrote: > > > >> 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 object names. That's why > we > >> have a way to force case sensitivity for strings. > >> > >> > >> I'm sure there are other ways to do this - with custom properties for > >>> example. But I can't think of any practical downside to using the > button > >>> names, although I'm ready to hear any. > >>> > >> > >> I'm of the school that also avoids duplicate object names. In this case > I'd > >> probably name the buttons with a space and a number after the duplicate > part > >> of the name, and then when processing them, refer to "word 1 of the > short > >> name of btn x" to get the necessary info. > >> > >> -- > >> Jacqueline Landman Gay | jac...@hyperactivesw.com > >> HyperActive Software | http://www.hyperactivesw.com > >> > >> > >> ______________________________**_________________ > >> use-livecode mailing list > >> use-livecode@lists.runrev.com > >> Please visit this url to subscribe, unsubscribe and manage your > >> subscription preferences: > >> http://lists.runrev.com/**mailman/listinfo/use-livecode< > http://lists.runrev.com/mailman/listinfo/use-livecode> > >> > >> > > _______________________________________________ > > use-livecode mailing list > > use-livecode@lists.runrev.com > > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > > http://lists.runrev.com/mailman/listinfo/use-livecode > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
