geniusclown
Magician
Joined: 23 Apr 2003
Posts: 358
Location: USA
|
 Posted: Fri Oct 28, 2011 1:36 pm
Ironic bug? - Script Debugger
|
To reproduce this bug:
1) open script debugger (Tools>Script Debugger or #DEBUG from command line)
2) in the class tree, expand the tree of my active package
3) deselect any number of classes (one will do)
Effect: The script debugger stops showing any processes within that package whether or not they're in the deselected class. Lines that are sent to other windows (and thus have their own trees in the debugger) are still displayed, but without the code that created it.
Without the ability to filter out the extremely spammy scripts that I'm 99% sure are not the cause of my lockups, the purpose of the script debugger is almost defeated. Certainly it's very difficult to use. |
|
