--- MisterX <[EMAIL PROTECTED]> wrote: > Hi Tim, > > Variable checking is one of my favorite > features. > > It checks that: > - all variables are declared > -- local whatever > -- if you use "it" without a previous "Get" > however > -- it will flag an error (as if i couldn't > get something > -- another way (do "get the time") - and that > won't be > -- noticed. Just use a <get zero> handler > before. > - All messages sent must be en-quoted if > literals. > -- local x > -- send "mouseup" to btn x > -- Mouseup must be enquoted. > > It's extremelly useful after you've written a > long script and > you need to debug any errors, it finds any > mispelled variables, > and best of all, in most cases, it takes less > time to be compliant > with variablechecking than it takes to find > bugs. > > Alas, one problem: if you hover the mouse over > a script that is > not compliant (and you have a mouseenter > script), there may be > triggers sent to the revErrorDisplay blocking > execution... And > this can go unoticed if you're not used to > it...
thanks, very useful exposition. what about parameters? i am declaring all my variables as script variables to see how that works. i have favor-ite variables like: pTarg, i, pCon etc. that turn up repeated in the Variable Watcher- pTarg pTarg when i am in the called handler. it don't seem right! Erik Hansen [EMAIL PROTECTED] http://www.erikhansen.org ____________________________________________________ Yahoo! Sports Rekindle the Rivalries. Sign up for Fantasy Football http://football.fantasysports.yahoo.com _______________________________________________ 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
