enhancement request

[dunbarx at aol.com]

Larry.


Sure you didn't hit "paste" twice? Anyway. LC would "see" the field with the lowest layer number as the one to reference, if, say, you "put something into fld myInput". This, of course, is the field at the bottom.


As for a warning that you already have one of that name, there are instances where that sort of naming is desired, and we would then have others writing for an enhancement that eliminated that annoying warning.


I say, "Live it, or live with it"


Craig



-----Original Message-----
From: larry <larry at significantplanet.org>
To: use-livecode <use-livecode at lists.runrev.com>
Sent: Tue, Oct 14, 2014 4:17 pm
Subject: enhancement request


Hello,
I've had this situation before and had it again today, which cost me a couple of 
hours.

I dragged a new scrolling field onto my stack and named it "myInput".  I hit 
Ctrl C and Ctrl V to copy it.  I dragged the new field to a new position and 
named it "myOutput".

Somehow (I'm not sure how) I ended up with 2 fields named "myInput" one right 
over the top of the other one.

Then I put some text into the top myInput (not realizing there was a bottom one) 
and tried to do some stuff.  What was happening, is that LC was looking at the 
bottom (1st) field "myInput" and there was no text in that one.

So, of course, I got very strange behavior and used up a good portion of my rock 
collection.


Here is what I wish for: (and I do not know how to officially make the request, 
and this is where someone can help)

If I am so "ignorant" or "unattentive" ?  to make such a blunder, it would be 
really wonderful for LC to pop up a warning saying something like, "Hey Larry! 
Wake Up!  You already have a field named "myInput"!!!"

Know what I mean?

Thanks,
Larry
_______________________________________________
use-livecode mailing list
use-livecode at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode