A nasty problem arose yesterday, only just solved. When the user switched from PING to HTTP the graph drew at the bottom, not at the top as it was supposed. The reason was that residual PING results were making their way back into the graph, keeping the maximum artificially high. The reason was that the graph sub-panel, which controlled the generation of probe threads that did the actual PINGs or HTTPs queries, was getting duplicated and replaced but not destroyed every time the graph got resized. This was caused by separating off the initialise code for Graph into a separate routine and rerunning it whenever a resize occurred. The side effect was duplication of threads that couldn't be killed. Doh!