As probably many newbies do from time to time, I am learning the system splattering 'self halt' around, and once again slipped one into the wrong place where I should have used 'haltOnce' and had a massive number of pre-debugger windows come up. I managed to get it back this time with the user interrupt - but not always - and anyhow clearing so many debug windows is a pain. So..... could 'self halt' be made to monitor the rate that the halt windows appear, and when more than some value from one of them (say five per second) it starts getting ignored and shows a dialog asking the user if they really meant this and enable danger mode, or if they screwed up and want to revert the method containing the suspect 'halt'. Advanced features + button to close all debugger windows. + display the method showing the suspect 'self halt' Another thought, it would be useful to be able to see a list of 'self halts' throughout the system and the timestamp of when they were insert, and perhaps distinguish whether they were inserted by the user or came when the package was loaded - and so providing more functionality than just using the Finder to 'search source'. Another thought, are there any plans for a "breakpoint" facility, so that I don't dirty a package by only inserting 'self halt' to aid debugging. The effect would be just the same as a 'self halt' and even be compiled in to the bytecode as if it was but the source code remains pristine. This could be represented by a symbol that could be dragged through a code window to anywhere immediately following a statement separator. Perhaps the statement separator itself gets special significance as a point that could be activated as a debug point - and displayed using a big red font when it is active. anyhow, just musing.... -ben