> I'm just wondering how other people are dealing with debug > statements in > scripts, and if anyone has a better solution than mine. Right > now I put > a bunch of win.debug calls in my scripts. I don't like to > comment/uncomment them, because they're useful even when for > production > scripts. OTOH, win.debug pops up the debug window, which is > inappropriate for production scripts, and especially slows > down script execution. > So I usually add a static variable in my script and use it like this:
If you wanted a production debug that didn't interfere with anything, put your debug into variables and output them as balloon tips (miscplugin) or with the OSD plugin. It would be a non-interference with the user experience but it would give you the info you want :) David Troesch | Atlanta, GA | ICQ# 2333123 America: Land of the free, home of the mega-corps. http://tinyurl.com/4weom Funstuff: If you love me, you'll drop the charges. ------------------------ Yahoo! Groups Sponsor --------------------~--> Fair play? Video games influencing politics. Click and talk back! http://us.click.yahoo.com/T8sf5C/tzNLAA/TtwFAA/JV_rlB/TM --------------------------------------------------------------------~-> Attention: PowerPro's Web site has moved: http://www.ppro.org Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/power-pro/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
