Wilhelm Sanke wrote:
Apart from the parts of my own scripts that are unprotected I see a lot of extra code, some of which may belong to CRevGeneral
...
Maybe the last example could be one of the culprits that slow down execution (?)

and such as

"on mouseDoubleUp pButtonNo, pTarget
--not been handled
--pTarget set in suppress messages frontscript
if pTarget is empty
then put the long id of the target into pTarget
put revTargetStack(pTarget) into tStack
put the defaultStack into tDefaultStack
set the defaultStack to tStack
if the mode of stack tStack is not 0
then click at the clickLoc
set the defaultStack to tDefaultStack
end mouseDoubleUp"

Good sluething, Wilhelm.

It might be helpful to de-standalone it to take a look at exactly what's been included.

Once upon a time someone posted the info needed to strip the executable from the stack -- anyone make a utility for that?

A simpler diagnostic might be to have your app spit out a list of frontScripts, backScripts, and libraries, something like this:

on LogScripts
  put the frontScripts &cr& the stacksInUse &cr& the backScripts \
    in url ("file:ScriptList.txt")
end LogScripts

It might also be helpful to log messages within your standalone using the messageHandled message. This is undocumented, but to have that message sent you first turn on the messageMessages global property, then get your list of handlers:

on StartLoggingMessages
  set the messageMessages to true
end StartLoggingMessages

In a library somewhere you can include this:

on messageHandled
  global gMessageLog
  put the params && the long name of the target &cr after gMessageLog
  pass messageHandled
end messageHandled

And to dump it just use:

on CloseMessageLog
  global gMessageLog
  put gMessageLog into url ("file:MessageLog.txt")
end CloseMessageLog

These scripts are off the top of my head, so please forgive an errors.

--
 Richard Gaskin
 Fourth World Media Corporation
 ___________________________________________________________
 [EMAIL PROTECTED]       http://www.FourthWorld.com
_______________________________________________
metacard mailing list
[email protected]
http://lists.runrev.com/mailman/listinfo/metacard

Reply via email to