Hi,
I've did some thinking too! It looks like (not sure if it can be
relied on though) you can read back the last value written to the
message box, as in:
put msg into myMsgText
Given that this is true, you could maybe have a utility that first
write some "unlikely value" to the message box (maybe "!@
[EMAIL PROTECTED]".
Then scan the script(s) "executing" each statement and checking the
contents of the message box for the "unlikely value", if it has
changed then the last statement wrote to the message box!
Probably too hard to implement and maybe I don't have enough to think
about today!!!
All the Best and Have a GREAT Weekend!
Dave
On 1 Dec 2006, at 12:52, Mark Smith wrote:
Me too...
Thinking aloud, as it were, would a handler like this work?
on checkScript pScript
repeat for each line L in pScript
add 1 to lineCount
if "put" is in L AND "into" is not in L then put lineCount &
comma after possibleProblems
end repeat
put possibleProblems
end checkScript
I guess we'd need to consider "into msg" and "into message" etc...
as well as "before", "after" and so on...
If we had a completely reliable version, we could even have it
comment out those lines.
Or has anyone already done this?
Mark
On 1 Dec 2006, at 11:36, Dave wrote:
put the scaledScore["memoryforstories"] of field "data1" into msg
Has got me before now! They can be sooooo hard to find when you
are writing lots of stuff to the message box for debugging, and
then forget to delete just one of them! This is especially true in
a library stack, I had a rouge "put xxx" in a library that took me
ages to track down, I eventually found it in a in function a few
levels away from the main API Call!
I think an option that turned off the "put xxx" shortcut would be
a good idea!
All the Best
Dave
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
