Hi Robin,

in addition to the previous answers: the debugger works a little bit different
in the event order. Sometimes it is helpful to just switch the frame the debugger
is running in (debug options).

As for finding the "slow" parts without debugger:
Try measuring the "slow" part with a few protocol StringToFiles(),
which sometimes is more accurate than the profiler, and just for
kicks do another run with a wait window just before the do while,
to get a freshly garbage and event cleaned program.

HTH

thomas