6.0 contains a new feature (which I've not yet used :-) - in the message box there is a button (top right, looks kind of like a target symbol) when you click it, the editor shows you the source script line that caused the last output.

That might help you in this case ....

-- Alex.

On 04/05/2013 21:05, william humphrey wrote:
I remember reading somewhere that version 6.0 or maybe GLX2 script editor
has a way to find an orphaned "put".  Anybody have any suggestions? If I
search for every "put" in my 6500 lines of code it will take a while and my
eyes will go blurry reading each one to check if it is putting to the
message box or not. Maybe there would be a way to "turn off" having a PUT
go right to the message box unless you say "put variable in the message
box"?
_______________________________________________
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

Reply via email to