How's this proposal for making it super simple:
1. add win.debugpause(1) to stop the debug window from reacting to win.debug
calls.
win.debugpause(0) resumes logging.
win.debugpause() returns the current paused state
2. win.debugpause state is also toggled by the Pause button in the debug window
* with this new service, a script could easily start/stop debugging:
if(not win.debugpaused)
win.debugpaused(1) ;; stops
* simpler script code and no need to remove debug lines from development to
production versions:
now write many:
if(DEBUG)
win.debug(...)
with win.debugpause write one:
win.debugpause(0) ;; or 1
and many:
win.debug(...)
* a user could easily turn debugging on/off by pressing the Pause button (no
more "edit the script..." type
of instructions...)
While a log.powerpro script could be very useful for more sophisticated
debugging needs, the
win.debugpause service already fills an need, I think.
------------------------ Yahoo! Groups Sponsor --------------------~-->
Get Bzzzy! (real tools to help you find a job). Welcome to the Sweet Life.
http://us.click.yahoo.com/A77XvD/vlQLAA/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/
